From: Pedro Alves <palves@redhat.com>
To: Andrew Burgess <andrew.burgess@embecosm.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 1/4] gdb: Remove register class specific layout names.
Date: Thu, 21 May 2015 13:17:00 -0000 [thread overview]
Message-ID: <555DDAD8.2030109@redhat.com> (raw)
In-Reply-To: <20150521122510.GJ2880@embecosm.com>
On 05/21/2015 01:25 PM, Andrew Burgess wrote:
>
> * Pedro Alves <palves@redhat.com> [2015-05-21 09:12:45 +0100]:
>> Doesn't your series effectively make this bit in display_command dead?
>> (while before it would switch on the registers layout).
>
> Sorry for missing that use.
>
> You're right, it's certainly dead now, though before my patch it still
> didn't do anything, passing the '$FREGS', etc names to
> tui_set_layout_for_display_command would just cause the regs display
> to pop up with the default register set. (At least, that's all I
> ever see, and I don't think anything else is possible.)
Right, that's what I saw.
>
> Given that it's not worked for a while, I propose to just remove the
> above snippet (really having this in display seems nasty to me) and
> just move to layout being for layout adjustment, and 'tui reg' to
> change the displayed register set.
Agreed.
>
>> (We should probably
>> rename tui_set_layout_for_display_command too.)
>
> Done, it's now tui_set_layout_by_name.
>
>> I had never noticed these special register layouts before either. I'm not
>> at all adverse to removing them. Not all expressions that start with $ are
>> registers, and probably a better idea would be to have
>> a separate "displays" window (so displays would go to that window
>> instead of the command window when the TUI is active), so that the tui
>> could neatly show watched variables/random expressions too.
>
> Sounds like a good idea.
>
> New patch below.
OK.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2015-05-21 13:17 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
2015-05-21 11:34 ` Pedro Alves
2015-05-21 12:25 ` Andrew Burgess
2015-05-21 13:17 ` Pedro Alves [this message]
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-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-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=555DDAD8.2030109@redhat.com \
--to=palves@redhat.com \
--cc=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.org \
/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