Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Michael Eager <eager@eagerm.com>
To: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Remote Serial Protocol -- reply to '?' when target running
Date: Tue, 09 Aug 2016 17:34:00 -0000	[thread overview]
Message-ID: <57AA13FC.2000707@eagerm.com> (raw)

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.

The description for '?' is
   Indicate the reason the target halted. The reply is the
   same as for step and continue.

The description for Stop Reply Packet says the following:
   The ‘C’, ‘c’, ‘S’, ‘s’, ‘vCont’, ‘vAttach’, ‘vRun’, ‘vStopped’,
   and ‘?’ packets can receive any of the below as a reply. Except
   for ‘?’ and ‘vStopped’, that reply is only returned when the
   target halts.

This suggests that the target can reply to '?' even if it is not
stopped, which seems to contradict the description for '?'.  But
none of the listed replies seem to be appropriate.  None of the
replies look like "Don't bother me, I'm busy".

How should the JTAG pod respond?  What do most do in this situation?

-- 
Michael Eager	 eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306  650-325-8077


             reply	other threads:[~2016-08-09 17:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-09 17:34 Michael Eager [this message]
2016-08-09 18:41 ` taylor, david
     [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=57AA13FC.2000707@eagerm.com \
    --to=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