From: Jim Blandy <jimb@codesourcery.com>
To: "xchen" <xchen@sunrisetelecom.com.cn>
Cc: <gdb@sourceware.org>
Subject: Re: gdbserver can't run over serial
Date: Tue, 02 Oct 2007 21:49:00 -0000 [thread overview]
Message-ID: <m3przxw5k6.fsf@codesourcery.com> (raw)
In-Reply-To: <20070929073901.E3B7911F80B@lax-gw07.mroute.net> (xchen@sunrisetelecom.com.cn's message of "Sat, 29 Sep 2007 15:39:43 +0800")
"xchen" <xchen at sunrisetelecom.com.cn> writes:
> Firstly gdb connected with gdbserver, then gdbserver was silent.
> Remotebaud was 9600 and remotedevice was /dev/ttyS0. I set debug remote 1
> and see lots of msg. But I don't understand it at all. Belowed is snapshot
>
> ./gdbserver /dev/ttyS0 hellogdb
> Process hellogdb created; pid = 245
> Remote debugging using /dev/ttyS0
If you're curious, the remote protocol is documented in Appendix D of
the GDB manual. Your transcript at least shows that gdb and gdbserver
are talking to each other happily.
If you were to simply run 'hellogdb' instead of './gdbserver
... hellogdb', where would hellogdb's stdout go? Would it go to
/dev/ttyS0 too? If so: GDB silently consumes any extraneous
characters it receives between packets, so GDB may be simply eating
your output.
next parent reply other threads:[~2007-10-02 21:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070929073901.E3B7911F80B@lax-gw07.mroute.net>
2007-10-02 21:49 ` Jim Blandy [this message]
2007-09-29 8:05 xchen
-- strict thread matches above, loose matches on Subject: below --
2007-09-29 8:05 xchen
2007-09-29 8:05 xchen
2007-09-29 8:05 xchen
2007-09-29 8:05 xchen
2007-09-29 8:05 xchen
2007-09-29 8:05 xchen
2007-09-29 8:05 xchen
2007-09-29 8:05 xchen
2007-09-29 8:05 xchen
2007-09-29 8:05 xchen
2007-09-29 8:05 xchen
2007-09-29 8:05 xchen
2007-09-29 8:05 xchen
2007-09-29 8:05 xchen
2007-09-29 8:05 xchen
2007-09-29 8:05 xchen
2007-09-29 8:05 xchen
2007-09-29 8:05 xchen
2007-09-29 8:05 xchen
2007-09-29 8:05 xchen
2007-09-29 8:05 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=m3przxw5k6.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