From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19217 invoked by alias); 29 Sep 2003 21:17:49 -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 19198 invoked from network); 29 Sep 2003 21:17:46 -0000 Received: from unknown (HELO localhost.redhat.com) (207.219.125.105) by sources.redhat.com with SMTP; 29 Sep 2003 21:17:46 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id BDFFA2B89; Mon, 29 Sep 2003 17:17:44 -0400 (EDT) Message-ID: <3F78A178.5000302@redhat.com> Date: Mon, 29 Sep 2003 21:17:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030820 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Daniel Jacobowitz Cc: gdb-patches@sources.redhat.com Subject: Re: RFA/RFC: vCont for the remote protocol [doco] References: <20030929152911.GA23320@nevyn.them.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-09/txt/msg00641.txt.bz2 > -@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. ... first non-alpabetic character, if any. Unless you want to pin down the terminator? I think ";" will work better as, in the below, it better separates out the separate actions. > +@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 No. The behavior shall be identical to the other continuation packets. If it isn't recognized, "" is returned. You may find it useful to clarify the spec so that a separate probe is possible vis -> vCont <- Enn or OK or Tnn? || -> vCont <- speaking of which. What happens if vCont specifies nothing? Return a dummy Tnn packet? Return 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. Andrew