From mboxrd@z Thu Jan 1 00:00:00 1970 From: elf@florence.buici.com To: xavier Cc: ecos-discuss@sources.redhat.com Subject: Re: [ECOS] GDB stubs problem Date: Mon, 28 May 2001 10:12:00 -0000 Message-id: <20010528101237.A26590@buici.com> References: <000f01c0e76f$96fea1f0$db2314ac@rt3880> X-SW-Source: 2001-05/msg00466.html I've had the same problem. Are you, by chance, trying to use gdb5.0 for x86? If so, try the gdb that comes with your Linux distrubution. I found that gdb5.0 didn't work. On Mon, May 28, 2001 at 08:13:22PM +0800, xavier wrote: > > Hi, > > I'm trying GDB stubs support in eCos. I build both gdb_module.img and > a test program with GDB stubs included. When the gdb_module.img > starts in the target, it sends the following packet: > > ++$T0525:a0307a34;1d:80005420;#2 > > It seems OK. The gdb_module is waiting for a connection. Then I connect > GDB to the target. The target receives the following packet: > > +$H9$Hc9$Hc9$Hc9---+$4$qC4$qC4$qC4---+$b$qOb$qOb$qOb---+ > > (gdb) target remote com1 > Remote debugging using com1 > Ignoring packet error, continuing... > Ignoring packet error, continuing... > Ignoring packet error, continuing... > Couldn't establish connection to remote target > Malformed response to offset query, timeout > (gdb) > > I looked into the source code and found that in getpacket() in generic-stubs.c, > __add_char_to_packet() expects a '#' character to finish a packet but there is > no '#' character sent from GDB. So getpacket() ran forever. > > Any suggestion? >