From: Eli Zaretskii <eliz@gnu.org>
To: Yao Qi <yao@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Teach -data-list-register-values to not include unavailable registers
Date: Fri, 07 Jun 2013 14:29:00 -0000 [thread overview]
Message-ID: <83sj0ut2ob.fsf@gnu.org> (raw)
In-Reply-To: <1370609650-23595-1-git-send-email-yao@codesourcery.com>
> 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.
next prev parent reply other threads:[~2013-06-07 14:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-07 12:53 Yao Qi
2013-06-07 14:29 ` Eli Zaretskii [this message]
2013-06-07 20:09 ` Pedro Alves
2013-06-07 20:40 ` Pedro Alves
2013-06-08 3:48 ` Yao Qi
2013-06-08 5:21 ` Eli Zaretskii
2013-06-17 11:20 ` [ping]: " Yao Qi
2013-06-18 15:24 ` Tom Tromey
2013-06-19 10:03 ` Yao Qi
2013-06-19 19:07 ` Tom Tromey
2013-06-20 4:59 ` Yao Qi
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=83sj0ut2ob.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=yao@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