• Locked Locked
  • Replies 2 replies
  • Subscribers 54 subscribers
  • Views 318 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Linux CCS v5 M8.5 stability issues...

Joe Cossette
Intellectual 780 points


Was conducting a dual debug session on TI8148 Linux-based target with both JTAG and GDB, debugging a kernel driver via JTAG and the application program that uses the driver via GDB.  Got pretty far into the session and everything was going fine.  Then when I was GDB stepping after interspersed debug types (at this point JTAG target was running, GDB only debug) the whole CCS GUI just disappeared.  Can't say for sure what exactly happened, but I can see that the GDB debugger process is still running in memory. After this I had to reboot because when I restarted CCS the emulator wouldn't initialize properly, no doubt the USB subsystem was probably in an inconsistent state.

When CCS dumps like this does it leave any logs or exception files around that might be of help? Is there anything I can set that might help you folks determine what this problem is? I've still got alot of debugging to do so I suspect that it'll happen again sooner or later. 

If it helps any the CCS host system is running Ubuntu 10.04 LTS.  The host H/W is an older 2.6Ghz pentium 4 w/1gb ram.    This system is slow enough already so I'd prefer to not slow it down too much more if possible.

 

 

  • TI__Expert 5985 points

    Joe,

    There should be a hs_err_pid<some number>.log file in the same folder as eclipse (<install>/ccsv5/eclipse/).  If so, please attach it to this thread.  If not, then likely that directory isn't writable.  In that case, modify eclipse.ini to add the following line at the end:

    -XX:ErrorFile=/path/to/somewhere/writable/hs_err_%p.log

    Then you can find the hs_err file in that folder and send it to us if it crashes again.

    Another option is to enable core dumps.  However, those are going to be huge, and there's a very good chance that all we'll need to debug is the hs_err file.

    A final option is to enable debugger logging (in help->ccs support).  However, that's going to slow down CCS somewhat, so that may not be an option for you unless you find a test case that's consistently reproducible.

    Darian

  • in reply to Darian Sale
    Intellectual 780 points

    No log file, no doubt due to the permissions.  I've tweaked the eclipse.ini per your instructions to have it log to my home directory in the .eclipse directory...this should do the trick as far as permissions are concerned.

    As soon as I can get it to happen again I'll check for the log file and up it to this thread.  Will also keep an eye out for ways to reproduce it if possible.