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.

CCS v5.1, a Linux app, and "Child terminated with signal"

Other Parts Discussed in Thread: LM137

I am trying to use the debugger in CCS 5.1.  I am using the community Linux distributions.  I have a relatively simple Linux app running on an LM137 eval board.  So far it simply manipulates I2C and GPIO, all from user space.  It prints to the serial console.  It runs reasonably well when the debugger is not engaged.  But when I try to run it under the debugger, the serial console ends with 

Child terminated with signal = 5

Child terminated with signal = 0x5 (SIGTRAP)
GDBserver exiting

The console window on CCS says

[New Thread 936]
Cannot access memory at address 0x0
Quit (expect signal SIGINT when the program is resumed)

This isn't obviously related to any action of my program. It happens later if I feed commands from a script or add a lot of tracing printfs. It's almost as if it happens a fixed number of seconds after startup.  I install my own sigint handler and it is not triggered.  Searching the community for sigint, I find a post about DSPBIOS installing handlers.  But I'm not using DSPBIOS, AFAIK.  

Does this sound familiar to anyone?  

Chuck

  • I guess this doesn't sound familiar to anyone.  I suppose I could again go through the installation procedure.  There are a lot of software components involved.  Maybe one of them isn't matched.  

    What do other people here do for a GUI debugger on a Linux application?  I don't mind using printf, but my team asks for more...

    Chuck