From: Jim Blandy <jimb@codesourcery.com>
To: "xchen" <xchen@sunrisetelecom.com.cn>
Cc: <gdb@sourceware.org>
Subject: Re: (Rising Spam Alert)gdbserver can't run over serial
Date: Tue, 02 Oct 2007 21:52:00 -0000 [thread overview]
Message-ID: <m3lkalw5el.fsf@codesourcery.com> (raw)
In-Reply-To: <20070929080553.740EF13B821@lax-gw04.mroute.net> (xchen@sunrisetelecom.com.cn's message of "Sat, 29 Sep 2007 16:06:37 +0800")
"xchen" <xchen at sunrisetelecom.com.cn> writes:
> This is the initial msg for gdb. Maybe useful.
>
> (gdb) target remote /dev/ttyS0
> Remote debugging using /dev/ttyS0
> Sending packet: $qSupported#37...Ack
> Packet received:
> Packet qSupported (supported-packets) is NOT supported
No, that's not a problem. The remote protocol specifies that, if a
stub receives a packet it doesn't understand, it should send back the
empty string as a reply. GDB tries using whatever packets it hopes
will work; if the stub says it doesn't understand them, then GDB tries
to find other ways to get the job done. So:
> Packet qSupported (supported-packets) is NOT supported
just means that GDB tried to send a 'qSupported' packet to the stub,
but the stub didn't understand it, and GDB has decided not to try
that again.
next parent reply other threads:[~2007-10-02 21:52 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070929080553.740EF13B821@lax-gw04.mroute.net>
2007-10-02 21:52 ` Jim Blandy [this message]
2007-09-29 14:58 xchen
-- strict thread matches above, loose matches on Subject: below --
2007-09-29 14:58 xchen
2007-09-29 14:58 xchen
2007-09-29 14:58 xchen
2007-09-29 14:58 xchen
2007-09-29 14:58 xchen
2007-09-29 14:58 xchen
2007-09-29 14:58 xchen
2007-09-29 14:58 xchen
2007-09-29 14:58 xchen
2007-09-29 14:58 xchen
2007-09-29 14:58 xchen
2007-09-29 14:58 xchen
2007-09-29 14:58 xchen
2007-09-29 14:58 xchen
2007-09-29 14:58 xchen
2007-09-29 14:58 xchen
2007-09-29 14:58 xchen
2007-09-29 14:58 xchen
2007-09-29 14:58 xchen
2007-09-29 14:58 xchen
2007-09-29 14:58 xchen
2007-09-29 14:58 xchen
2007-09-29 14:58 xchen
2007-09-29 14:58 xchen
2007-09-29 14:58 xchen
2007-09-29 14:58 xchen
2007-09-29 14:58 xchen
2007-09-29 14:58 xchen
2007-09-29 14:58 xchen
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=m3lkalw5el.fsf@codesourcery.com \
--to=jimb@codesourcery.com \
--cc=gdb@sourceware.org \
--cc=xchen@sunrisetelecom.com.cn \
/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