This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] Teach -data-list-register-values to not include unavailable registers
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Yao Qi <yao at codesourcery dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Fri, 07 Jun 2013 17:29:08 +0300
- Subject: Re: [PATCH] Teach -data-list-register-values to not include unavailable registers
- References: <1370609650-23595-1-git-send-email-yao at codesourcery dot com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> From: Yao Qi <yao@codesourcery.com>
> Date: Fri, 7 Jun 2013 20:54:10 +0800
>
> This patch adds an option --skip-unavailable to MI command
> -data-list-register-values, so that unavailable registers are not
> displayed (on the context of traceframes).
"Skip unavailable" is double negation. How about -show-available
instead?
> --- a/gdb/NEWS
> +++ b/gdb/NEWS
> @@ -76,6 +76,10 @@ show range-stepping
>
> ** The new command -dprintf-insert sets a dynamic printf breakpoint.
>
> + ** The command -data-list-register-values now accepts an optional
> + "--skip-unavailable" option. When used, only available registers
> + are displayed. ^^^^^^^^^^^^^^
"only the available"
> Display the registers' contents. @var{fmt} is the format according to
> which the registers' contents are to be returned, followed by an optional
> list of numbers specifying the registers to display. A missing list of
> -numbers indicates that the contents of all the registers must be returned.
> +numbers indicates that the contents of all the registers must be
> +returned. In the context of trace frames, the
> +@code{--skip-unavailable} option indicates that only available
> +(collected) registers are returned.
^^^^^^^^^^^^
"are to be returned". And why do you need the first part of that
sentence, about the "context of trace frames"? Does it add anything
to the description?
Thanks.