From: Pedro Alves <pedro@palves.net>
To: Luis Machado <luis.machado@arm.com>,
Andrew Burgess <aburgess@redhat.com>, Tom Tromey <tom@tromey.com>,
Luis Machado via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Fix crash with "maintenance print arc"
Date: Fri, 29 Apr 2022 12:25:19 +0100 [thread overview]
Message-ID: <9b53b5f1-8832-f1da-f3cc-f6cdc1b83cab@palves.net> (raw)
In-Reply-To: <f671f58f-325a-09e4-a254-67235f436137@arm.com>
On 2022-04-29 11:39, Luis Machado via Gdb-patches wrote:
> Ah, we have a "maint show" command. I wasn't aware of it until now.
>
> Isn't this particular behavior a bit strange though? "maintenance" will always output the maintenance prefix, except for "maintenance show", which removes the show part.
>
> It might be historical.
I think "maint show" is doing the same thing as "show". Note "help maint show" says it lists the
_variables_, not the commands to show each variable:
(gdb) help maint show
Show GDB internal variables used by the GDB maintainer.
Configure variables internal to GDB that aid in GDB's maintenance
...
"maint", "help show" and "help maint show" output a list of commands, thus with full prefix.
next prev parent reply other threads:[~2022-04-29 11:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 10:07 Luis Machado
2022-04-27 10:43 ` Andrew Burgess
2022-04-27 11:00 ` Luis Machado
2022-04-28 15:27 ` Tom Tromey
2022-04-29 10:20 ` Andrew Burgess
2022-04-28 15:26 ` Tom Tromey
2022-04-29 8:58 ` Luis Machado
2022-04-29 10:18 ` Andrew Burgess
2022-04-29 10:39 ` Luis Machado
2022-04-29 11:25 ` Pedro Alves [this message]
2022-05-05 9:31 ` Luis Machado
2022-05-27 13:34 ` 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=9b53b5f1-8832-f1da-f3cc-f6cdc1b83cab@palves.net \
--to=pedro@palves.net \
--cc=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=luis.machado@arm.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).