[ECOS] GDB "invalid remote reply"...

[Iztok Zupet]

On Tuesday 05 November 2002 19:22, Jonathan Larmour wrote:
> The target with a built-in stub won't be listening for GDB so when GDB
> tries to connect it won't reply. It will only listen for a ctrl-c (0x3).
> To force it to stop and listen for GDB, insert a call to breakpoint() at
> the point you want to start debugging your program.

That's true, the GDB can't connect to target stubs until they are initialized 
with the first call to breakpoint(). I must admit, I haven't looked at the 
eCos stub code yet, but at least the ones I patched and use for the AVR debug 
work that way. The first thing to do there in program is call breakpoint() or 
TRAP(),  then You can use continue in GDB.

Iztok

-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss