CodeComposer V5 has started to close or crash without explanation

I am using CCS V5 to develope code on the LM4F232H5QD EKS.

I was using CCS V5 yesterday without issue.  Starting today it has become unstable.  It is closing randomly when starting a debug session, stopping a debug session.  Also without change to code, my one interrupt was not hitting a breakpoint during one session and on the very next session it was hitting.

I am developing a library and have a main program that serves as its functional test.  I am having trouble duplicating when this happens, but it is happening frequently, every several minutes.

Is there a problem with starting to debug the functional test, stepping into a library or hitting a breakpoint in a library, then continuing?

I almost suspect that if I end the debug session while stopped in the library, the CCS project focus is set to the library.  Then, if I am not attentive, I start a new debug session, but the focus is on the library, so CCS tries to load the library bare and that is when CCS exits unceremoniously.  (just confirmed this happens.)

Any ideas?  I am tired of restarting CSS every few minutes.

Regardless,  CCS shouldn't just exit.

John

  • Hi John,

    how reproducable is this across projects and workspaces?  COuld you send any error logs or .dmp files generated?

    We are investigating something similar.   Any further details you could provide would be beneficial.

    Best Regards,
    Lisa

  • In reply to Lisa TI:

    I briefly looked for .dmp files, and did not find anything.  Where would I find them?

    I have been able to run several times by being very careful to highlight the functional test project and not the library project.  It is almost as if when the CCS has focus on a project other than the project with main() defined, starting or stopping a debug session exits CCS abruptly - and I mean abruptly - like gone in a flash. 

    I have had some other throw away workspaces and projects; this is my first project for keeps and my first project developing a library.

  • In reply to Lisa TI:

    I have also noticed that my projects that were not dependent on a library I was developing in tandem, when you close CCS and cycle power to the EKS, you program was still in there running.  With this function test/library development, the application does not seem to be retained.

  • In reply to John Osen:

    Hi John,

    A couple things.  First is you should get an error not a crash if you accidentally have the library project selected and press debug. You can not debug a library project.

    Is what you are trying to do actually step into a function that is located in a libarary?  This will cause problems are library projects/the .lib files they generate are just combined out files the that can not be debugged or loaded via the debugger.

    Does this help clarify?

    Which of the two situations are you?

    Best Regards,
    Lisa

  • In reply to Lisa TI:

    I definitely crash without an error if I accidentally have the library selected. 

    I find it surprising that I cannot debug the library as I do indeed set a breakpoint on a line in the source code for the library and I actually do break in that function.  I can also set a breakpoint out in the main() projects code and step into the library function.  So from my experience you can 'debug' a library, but after a few steps, CCS closes abruptly.  I am linking to the debug version of the library.

    So I am stepping into a library function.

    How do you debug library code as you are developing it?  Make it part of your main() project, then move over to the libary when it is working?  So what happens after release and you are fixing a defect in the library?  Move the module in question into and out of the main() project?

    How did your TI folks debug StellarisWare libraries?

    My workspace has both a project for the libary and a project for the main() application.

  • In reply to John Osen:

    Hi John,

    ok, let me see if I can find a comprehensive answer for you.

    The Stellarisware "libraries", if you mean like the drvlib and usblib etc are actually not library projects.

    Best Regards,
    Lisa

  • In reply to Lisa TI:

    Lisa,

    Thanks for your time looking into this.

    I realize the Stellaris libraries you reference are, for me, just libraries I link to and not projects.  But for the folks who developed them and who are now supporting them, I would assume they are projects. 

    I will not be surprised if there is some arcane option I need to select to avoid this issue.

    John

  • In reply to John Osen:

    Hi John,

    ok could you please explain a bit more what exactly you are trying to do.

    Usually a library is supporting code. Normally one would debug some main project which links to the library.  If you have the source for the library then stepping into the code etc should actually be ok and you should have the debug information there.  If you do not have the source or you only have a precompiled library this is where issues may occur.  Typically a main is not in a library and it is from your main you start debugging.

    The Stellarisware pieces I mentioned, are actually not library projects.  They are simply supporting projects that can be referenced by the main examples/your code.

    Does this helps clarify?

    Best Regards,
    Lisa

  • In reply to Lisa TI:

    I am developing my own library.  So I have two projects.  One contains the library.  One contains the main() function, which for now is testing the library during development,

    When I try to step into a library function, I am able to do so.  But at some random time, or if I exit the debugging session, with the PC somewhere in the library function, CCS abruptly exits with no error or dump.  This make debugging MY library difficult.

    I am not trying to debug StellarisWare libraries.  I am not under the impression that I can step into a StellarisWare function.  I am not trying to.  I only brought up StellarisWare because I know there is somebody at TI debugging libraries in order to support these StellarisWare libraries.  I do not believe the StellarisWare library TI dev team would easily suffer CCS abruptly exitting.  Hence, there is some difference between how I am configuring my CCS workspace or project.  Because the TI support team would be unlikely to accept the CCS behaviour I am seeing.

    I am not trying to debug StellarisWare libraries.

    I am trying to debug my own libraries, that I am just now starting to develop.  The editor keeps exiting.  I am tired of restarting CCS every few minutes when I am trying to step through MY library code.  I am not trying to step through StellarisWare code.

    Of the plethera of StellarisWare examples, I am not aware of any that develop a library.

  • In reply to John Osen:

    Hi John,

    as it seems you have the source obviously, I am wondering why you see the crashes then.  Would you at all be able to share the project offline, or at least a small portion where this occurs for us to try and reproduce?  There is no particular trigger that you noticed? 

    Best Regards,
    Lisa