From: Tom Tromey <tom@tromey.com>
To: Matthieu Longo via Gdb <gdb@sourceware.org>
Cc: Andrew Burgess <aburgess@redhat.com>,
Matthieu Longo <matthieu.longo@arm.com>
Subject: Re: Adding architecture-specific commands in GDB
Date: Fri, 04 Sep 2026 10:04:12 -0600 [thread overview]
Message-ID: <87o6ed0zr7.fsf@tromey.com> (raw)
In-Reply-To: <3ae21c49-6f06-4e84-8e33-de82e46ba53b@arm.com> (Matthieu Longo via Gdb's message of "Fri, 26 Jun 2026 09:52:53 +0100")
>>>>> "Matthieu" == Matthieu Longo via Gdb <gdb@sourceware.org> writes:
>> Maybe I'm wrong, in which case I'd love to see some counter examples,
>> but the set/show command are usually for settings that are set by the
>> user of GDB, and the show reads back the setting.
>>
>> Viewing kernel data would normally be an 'info' command.
Matthieu> What would the opposite of 'info' be ?
Matthieu> If for instance, I wanted to change a value in one of those tables ?
There isn't really one, but I guess you could introduce some new,
arch-specific prefix.
Somewhere I think there was some rationale for the show/info split,
though I no longer remember it. I'm not sure it is totally coherent any
more. But in most cases 'set' affects gdb, not the inferior. (Except
'set variable'. And other cases you may discover.)
Tom
next prev parent reply other threads:[~2026-09-04 16:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-22 16:26 Matthieu Longo via Gdb
2026-06-24 16:13 ` Andrew Burgess via Gdb
2026-06-26 8:52 ` Matthieu Longo via Gdb
2026-09-04 16:04 ` Tom Tromey [this message]
2026-09-07 17:28 ` Basile STARYNKEVITCH
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=87o6ed0zr7.fsf@tromey.com \
--to=tom@tromey.com \
--cc=aburgess@redhat.com \
--cc=gdb@sourceware.org \
--cc=matthieu.longo@arm.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