From: "ariga masahiro" <ariga@link-lab.co.jp>
To: <gdb@sourceware.org>
Subject: Re: Does not stop at break point in GDB-remote
Date: Tue, 15 Sep 2009 07:16:00 -0000 [thread overview]
Message-ID: <FCBEB468C19B4BACA765F31D9874D653@ariga> (raw)
Hello,
I understood a little bit of GDB remote serial protocol.
And I newly perused remote-5.log file.
--- excerpts from remote-5.log : break,continue commands
c b cyg_start ; break command
c c ; continue command
w $Z0,411dda,2#d3 ; Insert (`Z0') a memory breakpoint at
address 411dda of size 2
r +$#00
w +$m411dda,2#8a ; Insight gets breakpoint address's
codes
r +$1aa2#25
w +$X411dda,2:\x01\x80#30 ; Write address 411dda codes \x01\x80
r +$OK#9a
w +$vCont?#49
r +$#00
w +$Hc0#db
r +$OK#9a
w +$c#63 ; execute continue command
r
+$O4E6574776F726B20737461636B207573696E6720363936333220627974657320666F72206D6973632073706163650A#0C
w +
r
$O2020202020202020202020202020202020202020363936333220627974657320666F72206D627566730A#24
w +
r
$O202020202020202020202020202020202020202031333932363420627974657320666F72206D62756620636C7573746572730A#DF
w +
r
$O5B6379675F6E65745F696E69745D20496E69743A206D62696E69742830783030303030303030290A#60
w +
r
$O5B6379675F6E65745F696E69745D20496E69743A206379675F6E65745F696E69745F646576732830783030303030303030290A#32
w +
r $O496E697420646576696365202764703833393032615F65746830270A#FC
w +
r
$O4450383339303241202D20656570726F6D204553413A2030303A30323A63623A30313A34323A62390A#45
w +
r
$O5B6379675F6E65745F696E69745D20496E69743A206C6F6F706174746163682830783030303030303030290A#0D
w +
r
$O5B6379675F6E65745F696E69745D20496E69743A206966696E69742830783030303030303030290A#59
w +
r
$O5B6379675F6E65745F696E69745D20496E69743A20646F6D61696E696E69742830783030303030303030290A#2F
w +
r
$O5B6379675F6E65745F696E69745D20496E69743A206379675F6E65745F6164645F646F6D61696E2830783030343732386138290A#CF
w +
r $O4E657720646F6D61696E20696E7465726E657420617420307830303030303030300A#81
w +
r
$O5B6379675F6E65745F696E69745D20496E69743A206379675F6E65745F6164645F646F6D61696E2830783030343732323938290A#CE
w +
r $O4E657720646F6D61696E20726F75746520617420307830303030303030300A#2E
w +
r
$O5B6379675F6E65745F696E69745D20496E69743A2063616C6C5F726F7574655F696E69742830783030303030303030290A#5D
w +
r $O5B6379675F6E65745F696E69745D20446F6E650A#2D
w +
r +
w \x03 ; Here GDB stub's reply terminated,and GDB
sent "w \x03"
r <Timeout: -1 seconds>
End of log
---
What is "w \x03" ?
Because according to GDB remote serial protocol, it is reserved.
Any meaning ?
If you have any idea why GDB stub terminated reply,please teach me.
Masahiro Ariga
next reply other threads:[~2009-09-15 7:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-15 7:16 ariga masahiro [this message]
2009-09-15 15:16 ` Doug Evans
2009-09-16 6:58 ` ariga masahiro
2009-09-16 7:04 ` Hui Zhu
2009-09-16 7:25 ` Jeremy Bennett
-- strict thread matches above, loose matches on Subject: below --
2009-09-10 4:15 ariga masahiro
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=FCBEB468C19B4BACA765F31D9874D653@ariga \
--to=ariga@link-lab.co.jp \
--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