From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-27440-listarch-gdb-patches=sources.redhat.com@sources.redhat.com>
Received: (qmail 20298 invoked by alias); 1 Oct 2003 14:32:29 -0000
Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-patches-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sources.redhat.com>
List-Help: <mailto:gdb-patches-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-patches-owner@sources.redhat.com
Received: (qmail 20278 invoked from network); 1 Oct 2003 14:32:29 -0000
Received: from unknown (HELO localhost.redhat.com) (207.219.125.105)
  by sources.redhat.com with SMTP; 1 Oct 2003 14:32:29 -0000
Received: from redhat.com (localhost [127.0.0.1])
	by localhost.redhat.com (Postfix) with ESMTP
	id 0694B2B89; Wed,  1 Oct 2003 10:32:29 -0400 (EDT)
Message-ID: <3F7AE57C.3080100@redhat.com>
Date: Wed, 01 Oct 2003 14:32:00 -0000
From: Andrew Cagney <ac131313@redhat.com>
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 <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [v2] Re: RFA/RFC: vCont for the remote protocol [doco]
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> <20030930211640.GA19869@nevyn.them.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-SW-Source: 2003-10/txt/msg00001.txt.bz2

Looks good.  Can you send it as a formal proposal (as a protocol change) 
to gdb@, then give it a week?

Andrew

> -@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:

Should it specify that no action is also an error?

> +@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.

Hmm, yes good catch remembering to include ";".

> +@item empty

The convention:

	@item

is currently used for an empty packet.

> +The @code{vCont} packet is not supported.
> +@end table