From: Eli Zaretskii <eliz@gnu.org>
To: Yao Qi <yao@codesourcery.com>
Cc: palves@redhat.com, gdb-patches@sourceware.org
Subject: Re: [PATCH] Teach -data-list-register-values to not include unavailable registers
Date: Sat, 08 Jun 2013 05:21:00 -0000 [thread overview]
Message-ID: <831u8dtg9u.fsf@gnu.org> (raw)
In-Reply-To: <51B28F73.30301@codesourcery.com>
> Date: Sat, 8 Jun 2013 09:57:07 +0800
> From: Yao Qi <yao@codesourcery.com>
> CC: Eli Zaretskii <eliz@gnu.org>, <gdb-patches@sourceware.org>
>
> >> + ** The command -data-list-register-values now accepts an optional
> >> + "--skip-unavailable" option. When used, only available registers
> >> + are displayed. ^^^^^^^^^^^^^^
> >
> > "only the available"
> >
>
> Fixed.
>
> On 06/08/2013 03:58 AM, Pedro Alves wrote:
> >> "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.
>
> OK, the "context of trace frames" is removed. Here is the updated
> patch.
Fine with me, thanks.
next prev parent reply other threads:[~2013-06-08 3:48 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
2013-06-07 20:40 ` Pedro Alves
2013-06-08 3:48 ` Yao Qi
2013-06-08 5:21 ` Eli Zaretskii [this message]
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=831u8dtg9u.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--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