From: "taylor, david" <david.taylor@emc.com>
To: Michael Eager <eager@eagerm.com>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: RE: Remote Serial Protocol -- reply to '?' when target running
Date: Tue, 09 Aug 2016 18:41:00 -0000 [thread overview]
Message-ID: <63F1AEE13FAE864586D589C671A6E18B06C467@MX203CL03.corp.emc.com> (raw)
In-Reply-To: <57AA13FC.2000707@eagerm.com>
> From: gdb-owner@sourceware.org [mailto:gdb-owner@sourceware.org] On
> Behalf Of Michael Eager
> When gdb connects to a remote target, it asks about
> features, and then sends a '?' packet, asking why the
> target is stopped. When the target connection is through
> a JTAG pod, the pod may be able to respond to the feature
> request, but not be able to determine what the current state of
> the target is, likely because it is not stopped. What should a
> JTAG pod reply in this case?
>
> The GDB Remote Protocol doc doesn't seem to be entirely consistent.
Sounds like you are in non-stop mode... our stub
In 'Remote Protocol Support for Non-Stop Mode' (part of appendix E), it says in part:
If all threads are running when the target receives the '?' packet,
or if the target is not attached to any process, it shall respond 'OK'.
I don’t know about others, but we operate in non-stop mode and if there
are no stopped threads, we respond with 'OK'.
next prev parent reply other threads:[~2016-08-09 18:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-09 17:34 Michael Eager
2016-08-09 18:41 ` taylor, david [this message]
[not found] ` <57AA2A19.2030509@eagerm.com>
2016-08-09 19:28 ` taylor, david
2016-08-09 19:33 ` Michael Eager
2016-08-09 19:15 ` Gareth McMullin
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=63F1AEE13FAE864586D589C671A6E18B06C467@MX203CL03.corp.emc.com \
--to=david.taylor@emc.com \
--cc=eager@eagerm.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