From: Andrew Burgess <andrew.burgess@embecosm.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/4] gdb: Remove register class specific layout names.
Date: Thu, 21 May 2015 11:33:00 -0000 [thread overview]
Message-ID: <20150521113311.GI2880@embecosm.com> (raw)
In-Reply-To: <555D9A69.3070409@redhat.com>
* Pedro Alves <palves@redhat.com> [2015-05-21 09:42:17 +0100]:
> On 05/21/2015 12:17 AM, Andrew Burgess wrote:
> >
> > Second there is already the command 'tui reg GROUP' command to set the
> > displayed register set to GROUP, so making the layout command also
> > control the register set feels like unnecessary overloading of the
> > layout command.
>
> (A tangent: I was playing with this a bit now, and found it quite odd
> that there's a "tui reg next" command here, but
> no "tui reg previous"...)
Indeed, this is on my list of things to look at next (unless you're
already fixing it).
You'll also notice, at least on x86-64 that if you use 'tui reg next'
you get access to more register sets that are offered in the
tab-completion mechanism. This too is something I plan to address in
the next series.
Thanks,
Andrew
next prev parent reply other threads:[~2015-05-21 11:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 23:17 [PATCH 0/4] layout command changes Andrew Burgess
2015-05-20 23:18 ` [PATCH 1/4] gdb: Remove register class specific layout names Andrew Burgess
2015-05-21 8:42 ` Pedro Alves
2015-05-21 11:33 ` Andrew Burgess [this message]
2015-05-21 11:34 ` Pedro Alves
2015-05-21 12:25 ` Andrew Burgess
2015-05-21 13:17 ` Pedro Alves
2015-05-20 23:18 ` [PATCH 3/4] gdb: Don't call tui_enable too early Andrew Burgess
2015-05-20 23:18 ` [PATCH 4/4] gdb: Add cleanup to avoid memory leak on error Andrew Burgess
2015-05-20 23:18 ` [PATCH 2/4] gdb: Add completer for layout command Andrew Burgess
2015-05-21 0:25 ` Keith Seitz
2015-05-21 7:10 ` Andrew Burgess
2015-05-21 8:12 ` [PATCH 0/4] layout command changes Pedro Alves
2015-05-21 8:35 ` Pedro Alves
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=20150521113311.GI2880@embecosm.com \
--to=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).