From: Andrew Burgess <andrew.burgess@embecosm.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/3] Make "disassemble" always use TUI disassembly window
Date: Mon, 20 Jan 2020 00:48:00 -0000 [thread overview]
Message-ID: <20200119232327.GF3865@embecosm.com> (raw)
In-Reply-To: <877e1n43ct.fsf@tromey.com>
* Tom Tromey <tom@tromey.com> [2020-01-19 13:07:30 -0700]:
> >>>>> "Tom" == Tom Tromey <tom@tromey.com> writes:
>
> Tom> Currently the "disassemble" command will use the TUI disassembly
> Tom> window if it is already showing. I think it makes more sense to
> Tom> unconditionally switch to it. This patch implements this.
>
> I wonder if this should be limited to the case where the options to
> disassemble are compatible with what the TUI does.
I've wondered for a while if we should have something like:
set tui disassemble-flags ...
where a user can set the flags used by the disassembler. My main
interest initially was /r, but it might be nice if /m and /s could be
supported too, though I'm not quite sure how that might look or work.
Anyway, if we had something like this then using a disassemble command
could effectively be an alternative path to set the flags. So
something like:
(gdb) show tui disassemble-flags
TUI will disassemble using no flags.
(gdb) disassemble /r 0x.....
# TUI ASM window updates, and includes opcodes.
(gdb) show tui disassemble-flags
TUI will disassemble using flags /r.
# User doesn't want the opcodes any more, no problem.
(gdb) set tui disassemble-flags # <-- passing nothing here to
# clear the flags
# TUI updates, but not longer shows opcodes.
Just a thought.
Thanks,
Andrew
next prev parent reply other threads:[~2020-01-19 23:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-27 23:50 [PATCH 0/3] More TUI improvements Tom Tromey
2019-12-27 23:50 ` [PATCH 2/3] Make "disassemble" always use TUI disassembly window Tom Tromey
2020-01-19 20:08 ` Tom Tromey
2020-01-20 0:48 ` Andrew Burgess [this message]
2020-01-23 19:54 ` Tom Tromey
2019-12-27 23:50 ` [PATCH 1/3] Make "file" clear TUI source window Tom Tromey
2019-12-27 23:50 ` [PATCH 3/3] Remove flickering from the TUI Tom Tromey
2020-01-19 20:10 ` [PATCH 0/3] More TUI improvements Tom Tromey
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=20200119232327.GF3865@embecosm.com \
--to=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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