Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: RFA/RFC: vCont for the remote protocol [doco]
Date: Mon, 29 Sep 2003 15:29:00 -0000	[thread overview]
Message-ID: <20030929152911.GA23320@nevyn.them.org> (raw)

Documentation, as promised.  Reserves the `v' letter for multi-letter
packets.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

2003-09-29  Daniel Jacobowitz  <drow@mvista.com>

	* gdb.texinfo (Remote Protocol): Document v and vCont.

Index: doc/gdb.texinfo
===================================================================
RCS file: /big/fsf/rsync/src-cvs/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.175
diff -u -p -r1.175 gdb.texinfo
--- doc/gdb.texinfo	9 Aug 2003 15:10:09 -0000	1.175
+++ doc/gdb.texinfo	29 Sep 2003 14:32:55 -0000
@@ -19781,9 +19781,33 @@ Reserved for future use.
 
 Reserved for future use.
 
-@item @code{v} --- reserved
+@item @code{v} --- verbose packet prefix
 
-Reserved for future use.
+Packets starting with @code{v} are identified by a multi-letter name,
+up to the first @code{:} if any.
+
+@item @code{vCont:}[@var{action}@code{:}@var{tid}@code{;}]...[@var{action}] --- extended resume
+@cindex @code{vCont} packet
+
+Resume the inferior.  Different actions may be specified for each thread.
+If a final action is specified, then it is applied to all threads not
+explicitly mentioned; if no final action is specified, all other threads
+should remain stopped.  Possible actions are @code{s}, @code{S}@var{sig},
+@code{c}, and @code{C}@var{sig}, with the same meanings as those packets.
+The final @var{addr} associated with those packets is not supported in
+@code{vCont}.  Thread IDs are specified in hexadecimal.
+
+First reply:
+@table @samp
+@item OK
+for success
+@item E@var{NN}
+for an error
+@end table
+
+If the first reply is @samp{OK}, then the inferior will be resumed, and
+another reply sent when it stops.  @xref{Stop Reply Packets}, for the reply
+specifications.
 
 @item @code{V} --- reserved
 


             reply	other threads:[~2003-09-29 15:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-29 15:29 Daniel Jacobowitz [this message]
2003-09-29 21:17 ` Andrew Cagney
2003-09-29 21:25   ` Daniel Jacobowitz
2003-09-30 14:37     ` Andrew Cagney
2003-09-30 14:51       ` Daniel Jacobowitz
2003-09-30 15:37         ` Andrew Cagney
2003-09-30 21:16           ` [v2] " Daniel Jacobowitz
2003-10-01 14:32             ` Andrew Cagney
2003-10-10  2:21               ` Andrew Cagney

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=20030929152911.GA23320@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb-patches@sources.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