Re: RFA/RFC: vCont for the remote protocol [doco]

[Andrew Cagney <ac131313@redhat.com>]

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