Hi Vikas,
thank you for the answer - unfortunately, the mentioned work-around did not help. I renamed the "TraceServer.exe" and tried several times to run a debug session, but the behavior is still the same. Each time I stop the debug session CCS crashes...
I observed the situation a bit and found out some more details that may be helpful for your investigations:
1) in the "CCS edit perspective" I always have a window open for the target configurations -> Window > Show View > Target Configurations. To start a debug session I do a right click on the target configuration file "<project>.ccxml", which is visible in this window, and then I click on the context menu item "Launch Selected Configuration". After a short moment CCS switches to the "CCS debug perspective" and the debug session is open and running. If I stop the debug session now without doing any connection to a processor core, the CCS terminates the debug session and comes normally back to the "CCS edit perspective" without crashing - but the target configurations window is gone / closed.
2) if I start a debug session and I connect at least once to any processor core, than I can be sure that CCS will crash as soon as I try to stop the debug session. Even if I do a proper core reset and disconnect...
Note: starting the debug session by means of a target configuration or a debug configuration makes no difference for the two depicted scenarios.
Please let me know if I can or should do any other test to get more information on the root cause of this issue.
Kind Regards,
Stéphane