This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [DOC/RFA] point stub implementers towards the vCont packet
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Pedro Alves <pedro at codesourcery dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Tue, 17 May 2011 09:21:04 -0400
- Subject: Re: [DOC/RFA] point stub implementers towards the vCont packet
- References: <201105171338.49226.pedro@codesourcery.com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> From: Pedro Alves <pedro@codesourcery.com>
> Date: Tue, 17 May 2011 13:38:49 +0100
>
> vCont was added back in 2003 to overcome limitations of the
> s/c/S/C/Hc packets, but we still see people implementing them.
>
> I'm hoping this helps prevent that further.
>
> Okay to apply?
Yes, with a couple of gotchas:
> +At a minimum, a stub is required to support the @samp{g}, @samp{G}
"the @samp{g} and @samp{G} commands" is better.
> +(step) @var{command}s. Stubs that support multi-threading targets
> +should support the @samp{vCont} command. All other @var{command}s are
> optional.
There's no need to use @var here, as you use "command" as a literal
word, and the relation to @var{command} in the packet being documented
is clear.
Thanks.