From: Yao Qi <yao@codesourcery.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Pedro Alves <palves@redhat.com>, Eli Zaretskii <eliz@gnu.org>,
<gdb-patches@sourceware.org>
Subject: Re: [PATCH] Teach -data-list-register-values to not include unavailable registers
Date: Thu, 20 Jun 2013 04:59:00 -0000 [thread overview]
Message-ID: <51C24F95.7090008@codesourcery.com> (raw)
In-Reply-To: <87ehbx2a71.fsf@fleche.redhat.com>
On 06/20/2013 03:05 AM, Tom Tromey wrote:
> Yao> Processor may have a large number of registers, and users are only
> Yao> interested in collected or available registers in a traceframe. In
> Yao> this case, it is not useful to show (a large of number of) unavailable
> Yao> registers.
>
> I suppose if anybody cares they can request the information twice.
>
> The code bits are ok.
Thanks. Patch is committed.
--
Yao (é½å°§)
prev parent reply other threads:[~2013-06-20 0:41 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
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 [this message]
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=51C24F95.7090008@codesourcery.com \
--to=yao@codesourcery.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=tromey@redhat.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