From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [DOC/RFA] point stub implementers towards the vCont packet
Date: Tue, 17 May 2011 13:21:00 -0000 [thread overview]
Message-ID: <E1QMKCu-00025S-8c@fencepost.gnu.org> (raw)
In-Reply-To: <201105171338.49226.pedro@codesourcery.com> (message from Pedro Alves on Tue, 17 May 2011 13:38:49 +0100)
> 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.
next prev parent reply other threads:[~2011-05-17 13:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 12:39 Pedro Alves
2011-05-17 13:21 ` Eli Zaretskii [this message]
2011-05-17 13:31 ` Pedro Alves
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1QMKCu-00025S-8c@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox