Re: [ECOS] SIGTRAP, Trace/breakpoint trap

[Jonathan Larmour <jlarmour at redhat dot co dot uk>]

royston.choo@delphiauto.com wrote:
> 
> Has anyone seen SIGTRAP error while running (continue) GDB Insight?
> error message: "Program received signal SIGTRAP, Trace/breakpoint trap"
> 
> I thought it could be an exception, where can I trace down this trap?

This generally happens because the program has hit a breakpoint where GDB
doesn't think there should be one. A common case is if the board resets, at
which point the boot ROM on the board will deliberately hit a breakpoint
instruction (on most targets anyway).

Another common case is if the application does not co-operate with the GDB
stub in the ROM, _and_ the application doesn't have GDB stubs embedded
itself. If this is the case, generally you can successfully hit *one*
breakpoint, but never continue successfully from it. The fix is to include
GDB stubs in your app by enabling the appropriate option in the eCos
config.

To give a more definite answer, of course, I'd need to know your target,
platform, eCos version, ROM stub, whether you have GDB stubs included or
not, and in exactly what situation this happens anyway :-).

Jifl
-- 
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS  Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow."  ||  These opinions are all my own fault