public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: elf@florence.buici.com
To: xavier <xavierwang@ms19.url.com.tw>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] GDB stubs problem
Date: Mon, 28 May 2001 10:12:00 -0000	[thread overview]
Message-ID: <20010528101237.A26590@buici.com> (raw)
In-Reply-To: <000f01c0e76f$96fea1f0$db2314ac@rt3880>

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?
> 

  reply	other threads:[~2001-05-28 10:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-28  5:13 xavier
2001-05-28 10:12 ` elf [this message]
2001-05-28 22:41   ` xavier
2001-05-29  6:21     ` Gary Thomas
2013-02-01  2:00 [ECOS] gdb " Bob Cagle

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010528101237.A26590@buici.com \
    --to=elf@florence.buici.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=xavierwang@ms19.url.com.tw \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).