Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Yao Qi <yao@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Teach -data-list-register-values to not include unavailable registers
Date: Fri, 07 Jun 2013 20:09:00 -0000	[thread overview]
Message-ID: <51B23B65.8060309@redhat.com> (raw)
In-Reply-To: <83sj0ut2ob.fsf@gnu.org>

Replying for Yao as I wrote this.

On 06/07/2013 03:29 PM, Eli Zaretskii wrote:
>> 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?

I think I picked that because "unavailable" terminology is that is
what we've been using throughout GDB's output for such values.
We display then as literal "<unavailable>" (though also
"value not available").  For -show-available, it's
not as clear to me that "available" isn't just the generic english
word -- I'd have to ponder, 'does this include <error ...>,
'<optimized out>' values, etc. (the answer is yes, it does)? (*)
I'm obsessed about it, and this is machine interface anyhow, so
no user sees it.

(*) we seem to be lacking documentation of what all these
"<optimized out>", "<unavailable>" etc., values are.

>>  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?

Not really.  Meanwhile, we've added uses of <unavailable> outside trace
frames, so this it's really better to remove mention of trace frames.

-- 
Pedro Alves


  reply	other threads:[~2013-06-07 19:58 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
2013-06-07 20:09   ` Pedro Alves [this message]
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=51B23B65.8060309@redhat.com \
    --to=palves@redhat.com \
    --cc=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