Tool/software: Code Composer Studio
NOTE:
I also posted this as a reply on JohnS's answer in this forum post: https://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/565621
as because of the problem with the 'ctools.dll' solution explained below, I don't believe the issue I adequately resolved.
The problem:
I experienced the same 'Crash on Debug-session' problem as described in the post mentioned above. As soon as you start a debug session Code Composer Studio crashes:
Detailed description
When allowing it to be debugged with Visual Studio 2015 upon crashing it gives a more detailed description on the location of the problem:
"Unhandled exception at 0x5DE368C9 (DeviceIdentifier.dll) in ccstudio.exe: Stack cookie instrumentation code detected a stack-based buffer overrun."
Users with similar issues on the forum
Next to this post on the TI forum, the following (older) discussion also seemed to be experiencing a similar problem:
http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/564215/2073602
The rename 'ctools.dll' solution
As suggested, renaming the ctools.dll in ...\ccsv7\ccs_base\emulation\analysis\bin, seems to work around the problem, however, as also experienced by the users on the forum-post above, a new problem with System_printf()'s popup!
Re-installing all TI software
The problem seems to have started to occur either after and update in the Eclipse or when setting up new project / workspaces which require updates/installs of platform SDKs and/or xdctools (I am also using them from custom locations). So far I haven't found a way to get things working again at all.
Uninstalling and reinstalling al TI software didn't seem to resolved the problem (even when NOT using the web-installers). I've tried both reinstalling CCS 6.2 and the new CCS 7 (and also next to eachother). Un/reinstalling other tools like SmartRF Studio and Flash programming tools (or older versions thereof) also didn't provide a solution to the problem.
The weird thing is. Previously (still with CCS 6.2) everything was working properly, then suddenly I started having this problem.
In a way it also seems that somehow the computer got 'rigged' and since then is somehow not able to start debug sessions properly anymore.
I am running Windows 10 by the way.
I hope this issue can be resolved soon... or that a way can be found to repair and prevent the problem.
Thanks in advance,