From: Andrew Burgess <andrew.burgess@embecosm.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/2] Changes to show architecture/endian message
Date: Wed, 8 Jul 2020 09:54:53 +0100 [thread overview]
Message-ID: <cover.1594198122.git.andrew.burgess@embecosm.com> (raw)
I was recently debugging some issues around architecture selection so
had cause to use the 'show architecture' command.
The output from this command seemed ... not ideal to me, for example:
(gdb) set architecture mips
The target architecture is assumed to be mips
(gdb) show architecture
The target architecture is assumed to be mips
(gdb)
I don't like the use of 'assumed to be', this (to me) seems to imply
that GDB is making some assumptions on the users behalf. Even if we
interpret this to mean, GDB is assuming because the user told it, I
don't know why we don't just say:
(gdb) set architecture mips
The target architecture is set to "mips".
(gdb) show architecture
The target architecture is set to "mips".
(gdb)
Just say what you mean, the architecture was set to this value.
So, I made this and some other clean ups to the 'show architecture'
output.
Then while I was testing this I noticed that 'show endian' is
basically the same, so I changed that in a similar way.
Does the new output seem like an improvement to anyone else? Or does
anyone else prefer the old output?
Thanks,
Andrew
---
Andrew Burgess (2):
gdb: Improve formatting of 'show architecture' messages
gdb: Improve formatting of 'show endian' messages
gdb/ChangeLog | 4 +++
gdb/arch-utils.c | 14 ++++----
gdb/testsuite/ChangeLog | 8 +++++
gdb/testsuite/gdb.arch/amd64-osabi.exp | 2 +-
.../gdb.base/all-architectures.exp.tcl | 6 ++--
gdb/testsuite/gdb.base/attach-pie-noexec.exp | 4 +--
gdb/testsuite/gdb.base/catch-syscall.exp | 4 +--
gdb/testsuite/gdb.base/endian.exp | 34 +++++++++----------
gdb/testsuite/gdb.xml/tdesc-arch.exp | 6 ++--
9 files changed, 47 insertions(+), 35 deletions(-)
--
2.25.4
next reply other threads:[~2020-07-08 8:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 8:54 Andrew Burgess [this message]
2020-07-08 8:54 ` [PATCH 1/2] gdb: Improve formatting of 'show architecture' messages Andrew Burgess
2020-07-08 10:06 ` Gary Benson
2020-07-15 2:06 ` Simon Marchi
2020-07-15 9:36 ` Andrew Burgess
2020-07-17 15:52 ` Gary Benson
2020-07-08 8:54 ` [PATCH 2/2] gdb: Improve formatting of 'show endian' messages Andrew Burgess
2020-07-08 10:06 ` Gary Benson
2020-07-13 18:24 ` [PATCH 0/2] Changes to show architecture/endian message Tom Tromey
2020-07-14 12:27 ` [PUSHED " Andrew Burgess
2020-07-14 12:27 ` [PUSHED 1/2] gdb: Improve formatting of 'show architecture' messages Andrew Burgess
2020-07-14 12:27 ` [PUSHED 2/2] gdb: Improve formatting of 'show endian' messages Andrew Burgess
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=cover.1594198122.git.andrew.burgess@embecosm.com \
--to=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