This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Debugging multi-threaded eCos application using GDB
- To: Stefan Syberichs <Stefan dot Syberichs at ascom dot ch>
- Subject: Re: [ECOS] Debugging multi-threaded eCos application using GDB
- From: Jonathan Larmour <jlarmour at redhat dot com>
- Date: Fri, 03 Aug 2001 14:21:26 +0100
- CC: ecos-discuss at sources dot redhat dot com
- References: <OF834BFF37.952BB457-ONC1256A9D.00346E1C@hasler.ascom.ch>
Stefan Syberichs wrote:
>
> Hello,
>
> We have a similar problem like Nadine:
> Debugging an eCos application for the linux target is hard, because gdb is
> not aware of
> the eCos threads.
>
> > We do have some ideas on how to fix this properly, basically making
> > the thread-aware debugging inside gdb much more flexible, but so far
> > nobody has been willing to contribute or fund any of the work
> > involved.
>
> > Bart
>
> Bart, what exactly are the ideas for gdb ? Or does anybody have a solution
> meanwhile ?
Actually I would have thought the easiest route would be to allow included
stubs in the synth target to be available at a socket, and then using the
remote protocol. Making it available as a socket should "just" be a case of
adding a virtual vectored comm interface. It's probably a bit too much work
for us to just do for fun, particularly since the synth target doesn't use
virtual vectors at all right now.
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine