From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2030 invoked by alias); 30 Sep 2003 21:16:42 -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 1928 invoked from network); 30 Sep 2003 21:16:41 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sources.redhat.com with SMTP; 30 Sep 2003 21:16:41 -0000 Received: from drow by nevyn.them.org with local (Exim 4.22 #1 (Debian)) id 1A4RrM-0005Fq-Lr for ; Tue, 30 Sep 2003 17:16:40 -0400 Date: Tue, 30 Sep 2003 21:16:00 -0000 From: Daniel Jacobowitz To: gdb-patches@sources.redhat.com Subject: [v2] Re: RFA/RFC: vCont for the remote protocol [doco] Message-ID: <20030930211640.GA19869@nevyn.them.org> Mail-Followup-To: gdb-patches@sources.redhat.com References: <20030929152911.GA23320@nevyn.them.org> <3F78A178.5000302@redhat.com> <20030929212507.GA12032@nevyn.them.org> <3F799541.4070009@redhat.com> <20030930145103.GA26117@nevyn.them.org> <3F79A31C.8050403@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3F79A31C.8050403@redhat.com> User-Agent: Mutt/1.5.1i X-SW-Source: 2003-09/txt/msg00666.txt.bz2 On Tue, Sep 30, 2003 at 11:37:00AM -0400, Andrew Cagney wrote: > >packet ->> "vCont" { field }+ > >>field ->> ";" action [ ":" tid ] > >> > >>which is very easy to parse. BTW, intro has this to say, so there > >>aren't any guidelines :-( > > > > > >That loses the requirement that the default action be last, which I'd > >like to hold on to - OK? > > Was that to ensure that there wasn't more than one default action? I > think its better to instead clarify that in the text part of the spec vis: > > "By default all unspecified threads remain stopped. An action with no > corresponding {tdid} shall be applied to all threads with out an > explicitly specified action. A packet specifying multiple default > actions is erreneous." > > Looking at the new gdbserver code it's pratically doing this now. BTW, > I think it gets confused by the incorrect "...;cccccccccc", simplifying > to be strictly LL1 will fix that. This makes the stub parsing a little trickier, but not much. I don't think it does get confused by ";cccccccc"; if whatever you saw is still there in the revised version I'm about to post, please holler. > >I dislike the ';' because vCont is not an item in the list of actions > >that the semicolons are separating; that turns ';' from a separator > >into a prefix. But hey, prefixes are people too. > > Seperator or terminator? If it were a terminator we wouldn't need one at the beginning of the list. Here's updated docs. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer 2003-09-30 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 30 Sep 2003 19:42:01 -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 than other threads should remain stopped. Multiple default +actions are 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} +@item s +Step +@item S@var{sig} +Step with signal @var{sig} +@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 empty +The @code{vCont} packet is not supported. +@end table @item @code{V} --- reserved