From: Jeremy Bennett <jeremy.bennett@embecosm.com>
To: ariga masahiro <ariga@link-lab.co.jp>
Cc: Doug Evans <dje@google.com>, gdb@sourceware.org
Subject: Re: Does not stop at break point in GDB-remote
Date: Wed, 16 Sep 2009 07:25:00 -0000 [thread overview]
Message-ID: <1253085884.8100.96.camel@thomas> (raw)
In-Reply-To: <43B8D7FF75AE4627BF0FDB20BE51ED7E@ariga>
On Wed, 2009-09-16 at 15:57 +0900, ariga masahiro wrote:
> I understood \x03 command.
> I wish I could understand stub reply codes.
> Do you know any technique to analyse them ?
> If you happen to know how to debug stub,would you please teach me ?
> Or please refer me to any documents .
> I appreciate your help.
Hi Masahiro,
You may find this application note on how to write a Remote Serial
Protocol server useful:
http://www.embecosm.com/download/ean4.html
HTH,
Jeremy
--
Tel: +44 (1590) 610184
Cell: +44 (7970) 676050
SkypeID: jeremybennett
Email: jeremy.bennett@embecosm.com
Web: www.embecosm.com
next prev parent reply other threads:[~2009-09-16 7:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-15 7:16 ariga masahiro
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 [this message]
-- 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=1253085884.8100.96.camel@thomas \
--to=jeremy.bennett@embecosm.com \
--cc=ariga@link-lab.co.jp \
--cc=dje@google.com \
--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