From: David Paterson <dnpaterson@gmail.com>
To: John Smith <horserivers@gmail.com>
Cc: Pedro Alves <palves@redhat.com>, gdb <gdb@sourceware.org>
Subject: Re: what is the mean of remote protocol "S 00"?
Date: Mon, 04 Feb 2013 10:38:00 -0000 [thread overview]
Message-ID: <CAM1kHc2Q-y5aEwfuF8Wnp=2hXGnF_om5eAUcxsLnVjKAqR3Q5A@mail.gmail.com> (raw)
In-Reply-To: <CAJR88piFRecXLSKgh4xjJdVA7FfKZfjiaVjpSwrdr7wrkwSAwA@mail.gmail.com>
On 2 February 2013 04:43, John Smith <horserivers@gmail.com> wrote:
> That is saying I can not know the stop reason ?
> In this case , gdb will stop at the $eip in "g" packet， which is sent
> from the target side ?
> Is there method to know why the target stoped?
That really depends on your target and remote server.
You might be able to work out the reason by examining the call stack, or
looking at status or trap registers if your hardware has such things.
If the remote server can't give you a better indication of the stop reason, then
perhaps it's not possible to work it out, and it defaults to "00".
Regards,
David P.
prev parent reply other threads:[~2013-02-04 10:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-31 8:03 horseriver
2013-02-01 20:39 ` Pedro Alves
2013-02-02 4:43 ` John Smith
2013-02-04 10:38 ` David Paterson [this message]
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='CAM1kHc2Q-y5aEwfuF8Wnp=2hXGnF_om5eAUcxsLnVjKAqR3Q5A@mail.gmail.com' \
--to=dnpaterson@gmail.com \
--cc=gdb@sourceware.org \
--cc=horserivers@gmail.com \
--cc=palves@redhat.com \
/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