I don't know yet exactly what causes it, it's perhaps one of the following:
big source files? moving the mouse pointer too fast? typing too quickly? being a productive coder? coffein-allergy?
Perhaps a combination?
Goddamit. *frustrated*
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
I don't know yet exactly what causes it, it's perhaps one of the following:
big source files? moving the mouse pointer too fast? typing too quickly? being a productive coder? coffein-allergy?
Perhaps a combination?
Goddamit. *frustrated*
jap.. here we go again...
perhaps setting and resetting a brakepoint was too much hassle this time? or the Watch Locals window was too advanced a debugging method? dunno - dual monitors? cosmic rays?
Ohh yes! This time I didn't need to restart the computer. *happy*
Devor,
I agree, CCS crashes are quite frustrating.
My understanding is when CCS crashes it creates a dump file (*.dmp) in the <CCStudio Install Directory>\cc\bin\Logs directory. It would be good to send this file along with a description of what you were doing or a testcase to support@ti.com so the proper folks can look into it.
-Lori
Thnx for the answer. Unfortunatelly, these freezes do not produce dump files. :(
This is not merely frustrating, this is how you loose customers. It is entirely unacceptable to have CCS crashing during normal operation.