From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27958 invoked by alias); 10 Oct 2003 18:00:44 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 27951 invoked from network); 10 Oct 2003 18:00:42 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sources.redhat.com with SMTP; 10 Oct 2003 18:00:42 -0000 Received: from drow by nevyn.them.org with local (Exim 4.22 #1 (Debian)) id 1A81ZC-00087Z-07; Fri, 10 Oct 2003 14:00:42 -0400 Date: Fri, 10 Oct 2003 18:00:00 -0000 From: Daniel Jacobowitz To: gdb-patches@sources.redhat.com Cc: eliz@gnu.org Subject: [RFA/doc] vCont remote protocol packet, final version Message-ID: <20031010180041.GA31168@nevyn.them.org> Mail-Followup-To: gdb-patches@sources.redhat.com, eliz@gnu.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.1i X-SW-Source: 2003-10/txt/msg00365.txt.bz2 Hi Eli, The technical content of this patch has been finalized. Is the texinfo itself OK? -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer 2003-10-10 Daniel Jacobowitz * 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 10 Oct 2003 17:57:37 -0000 @@ -19781,9 +19781,51 @@ 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{;} or @code{?} (or the end of the packet). + +@item @code{vCont}[;@var{action}[@code{:}@var{tid}]]... --- extended resume +@cindex @code{vCont} packet + +Resume the inferior. Different actions may be specified for each thread. +If an action is specified with no @var{tid}, then it is applied to any +threads that don't have a specific action specified; if no default action is +specified then other threads should remain stopped. Specifying multiple +default actions is an error; specifying no actions is also an error. +Thread IDs are specified in hexadecimal. Currently supported actions are: + +@table @code +@item c +Continue. +@item C@var{sig} +Continue with signal @var{sig}. @var{sig} should be two hex digits. +@item s +Step. +@item S@var{sig} +Step with signal @var{sig}. @var{sig} should be two hex digits. +@end table + +The optional @var{addr} argument normally associated with these packets is +not supported in @code{vCont}. + +Reply: +@xref{Stop Reply Packets}, for the reply specifications. + +@item @code{vCont?} --- extended resume query +@cindex @code{vCont?} packet + +Query support for the @code{vCont} packet. + +Reply: +@table @samp +@item @code{vCont}[;@var{action}]... +The @code{vCont} packet is supported. Each @var{action} is a supported +command in the @code{vCont} packet. +@item +The @code{vCont} packet is not supported. +@end table @item @code{V} --- reserved