From: "xchen" <xchen@sunrisetelecom.com.cn>
To: "'xchen'" <xchen@sunrisetelecom.com.cn>, <gdb@sourceware.org>
Subject: RE: (Rising Spam Alert)gdbserver can't run over serial
Date: Sat, 29 Sep 2007 14:58:00 -0000 [thread overview]
Message-ID: <20070929145800.IUpeftIRhUlYAYouI2mfprAdQZyYcUg2UV31R4obAQo@z> (raw)
In-Reply-To:
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
-----Original Message-----
From: gdb-owner@sourceware.org [mailto:gdb-owner@sourceware.org] On Behalf
Of xchen
Sent: 2007年9月29日 15:40
To: gdb@sourceware.org
Subject: (Rising Spam Alert)gdbserver can't run over serial
Hi
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
============================================
(gdb) n
9 printf("hello the world\n");
(gdb) set debug remote 1
(gdb) n
Sending packet: $m100002a8,4#89...Ack
Packet received: 7c290b78
Sending packet: $M100002a8,4:7d821008#71...Ack Packet received: OK Sending
packet: $m10000414,4#57...Ack Packet received: 3d201000 Sending packet:
$M10000414,4:7d821008#3f...Ack Packet received: OK Sending packet:
$s#73...Ack Packet received: T0501:7ffffdc0;40:10000424; Sending packet:
$s#73...Ack Packet received: T0501:7ffffdc0;40:10000428; Sending packet:
$s#73...Ack Packet received: T0501:7ffffdc0;40:100109a0; Sending packet:
$m100109a0,4#89...Ack Packet received: 4bee3678 Sending packet:
$m1001099c,4#94...Ack Packet received: 4bffffcc Sending packet:
$m100109a0,4#89...Ack Packet received: 4bee3678 Sending packet:
$m1001099c,4#94...Ack Packet received: 4bffffcc Sending packet: $g#67...Ack
Packet received:
100004207ffffdc03001377010000824300170000000000a0000000100000000300180001000
0000000000007ffffd3022000022100189480000000000000000000000000000000000000000
00000000000000000000000000000000000000000ffecd180ffecd1800000001100004003002
6c387ffffe780ffea9287ffffdc0000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000
00000000100109a00000d032220000221000042c0ff04a880000000000000000
Sending packet: $m1000042c,4#87...Ack
Packet received: 3d201000
Sending packet: $m10000428,4#5c...Ack
Packet received: 48010579
Sending packet: $m1000042c,4#87...Ack
Packet received: 3d201000
Sending packet: $m10000428,4#5c...Ack
Packet received: 48010579
Sending packet: $m10000400,4#52...Ack
Packet received: 9421ffe0
Sending packet: $m10000404,4#56...Ack
Packet received: 7c0802a6
Sending packet: $m10000408,4#5a...Ack
Packet received: 93e1001c
Sending packet: $m1000040c,4#85...Ack
Packet received: 90010024
Sending packet: $m10000410,4#53...Ack
Packet received: 7c3f0b78
Sending packet: $m10000414,4#57...Ack
Packet received: 7d821008
Sending packet: $m7ffffdc0,4#93...Ack
Packet received: 7ffffde0
Sending packet: $m1000042c,4#87...Ack
Packet received: 3d201000
Sending packet: $M1000042c,4:7d821008#6f...Ack Packet received: OK Sending
packet: $c#63...Ack Packet received: T0501:7ffffdc0;40:1000042c; Sending
packet: $m10000428,4#5c...Ack Packet received: 48010579 Sending packet:
$m10000428,4#5c...Ack Packet received: 48010579 Sending packet:
$m10000400,4#52...Ack Packet received: 9421ffe0 Sending packet:
$m10000404,4#56...Ack Packet received: 7c0802a6 Sending packet:
$m10000408,4#5a...Ack Packet received: 93e1001c Sending packet:
$m1000040c,4#85...Ack Packet received: 90010024 Sending packet:
$m10000410,4#53...Ack Packet received: 7c3f0b78 Sending packet:
$m10000414,4#57...Ack Packet received: 7d821008 Sending packet:
$m7ffffdc0,4#93...Ack Packet received: 7ffffde0 Sending packet: $g#67...Ack
Packet received:
1000042c7ffffdc0300137700000001030017000000000100000000100000000000000000000
0010000000007ffffd3022000022100189480000000000000000000000000000000000000000
00000000000000000000000000000000000000000ffecd180ffecd1800000001100004003002
6c387ffffe780ffea9287ffffdc0000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000
000000001000042c0002d032220000221000042c0ff11f102000000000000000
Sending packet: $m1000042c,4#87...Ack
Packet received: 7d821008
Sending packet: $M1000042c,4:3d201000#5b...Ack Packet received: OK Sending
packet: $m100002a8,4#89...Ack Packet received: 7d821008 Sending packet:
$M100002a8,4:7c290b78#a9...Ack Packet received: OK Sending packet:
$m10000414,4#57...Ack Packet received: 7d821008 Sending packet:
$M10000414,4:3d201000#2b...Ack Packet received: OK
10 printf("please show me\n");
I run the program step by step, but gdbserver display nothing just halt on
Remote debugging using /dev/ttyS0. But if I quit gdb. The gdbserver will
quit too.
Thx,
Xi
next reply other threads:[~2007-09-29 8:05 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-29 14:58 xchen [this message]
[not found] <20070929080553.740EF13B821@lax-gw04.mroute.net>
2007-10-02 21:52 ` Jim Blandy
-- 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=20070929145800.IUpeftIRhUlYAYouI2mfprAdQZyYcUg2UV31R4obAQo@z \
--to=xchen@sunrisetelecom.com.cn \
--cc=gdb@sourceware.org \
/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