This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 2/2] Support single step by arch or target
- From: Pedro Alves <palves at redhat dot com>
- To: Yao Qi <qiyaoltc at gmail dot com>, gdb-patches at sourceware dot org
- Date: Tue, 15 Sep 2015 14:31:38 +0100
- Subject: Re: [PATCH 2/2] Support single step by arch or target
- Authentication-results: sourceware.org; auth=none
- References: <1441096915-23615-1-git-send-email-yao dot qi at linaro dot org> <1441096915-23615-3-git-send-email-yao dot qi at linaro dot org>
On 09/01/2015 09:41 AM, Yao Qi wrote:
> +@item vContSupported
> +This feature indicates whether @value{GDBN} wants to know the
> +supported actions in the reply to @samp{vCont?} packet.
> @end table
>
I find this confusing, because vCont? is already supposed
to return the supported vCont actions:
@item vCont?
@cindex @samp{vCont?} packet
Request a list of actions supported by the @samp{vCont} packet.
So ISTM that in the perspective of someone reading the manual without
the context we're discussing here, it's not clear at all what
vContSupported is supposed to mean and why not simply always
return the supported vCont actions in reply to vCont?
Is there an advantage to the vContSupported indirection? I was
originally thinking we'd make the server report "vCont=c;C;t;s;S;r"
directly in its qSupported reply, and gdb would stop using "vCont?"
going forward (if the target supports that qSupported feature).
Thanks,
Pedro Alves