Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@orcam.me.uk>
To: Guinevere Larsen <guinevere@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/2] gdb: introduce command "info architecture"
Date: Thu, 27 Nov 2025 20:00:22 +0000 (GMT)	[thread overview]
Message-ID: <alpine.DEB.2.21.2511271954290.36486@angie.orcam.me.uk> (raw)
In-Reply-To: <67dc2271-4c15-42d1-bd1a-d77e2cd1e6df@redhat.com>

On Thu, 27 Nov 2025, Guinevere Larsen wrote:

> >   We could reword output from `set architecture' so as not to suggest the
> > use without an argument is invalid.
> > 
> >   In any case the listing facility must not be an `info' subcommand, as
> > these are meant for showing the state of the debuggee,
> 
> I disagree, in my opinion, this new command would function basically just like
> "info unwinder", giving information on how GDB is able to interact with the
> inferior.

 Is it the semantics documented in the manual since forever (search for it 
and when it appeared there) that you disagree with?  I don't know what 
`info unwinder' is about, but maybe someone got it wrong too and it should 
be a `show' subcommand instead.

> >   while the set of
> > architectures supported is a property of the given instance of GDB itself,
> > and therefore suitable for the `set'/`show' commands.  So if a new command
> > it would have to be `show architecture list' or suchlike.
> 
> My understanding is that set/show commands are mostly used for when the user
> could change something, and the point of this command is showing the user the
> compilation options that were used, there's no changes that a user could do.

 Same as with:

(gdb) show version

-- it can't be changed by the user and there's no corresponding `set' 
command.

  Maciej

  reply	other threads:[~2025-11-27 20:01 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-06 19:45 [PATCH 0/2] Add warning if the native target is not supported Guinevere Larsen
2025-11-06 19:45 ` [PATCH 1/2] gdb: introduce command "info architecture" Guinevere Larsen
2025-11-06 23:24   ` Maciej W. Rozycki
2025-11-07 13:10     ` Guinevere Larsen
2025-11-07 15:51       ` Maciej W. Rozycki
2025-11-07 16:05         ` Hannes Domani
2025-11-08  2:02           ` Maciej W. Rozycki
2025-11-27 19:51         ` Guinevere Larsen
2025-11-27 20:00           ` Maciej W. Rozycki [this message]
2025-11-27 20:09             ` Guinevere Larsen
2025-11-28  9:20               ` Maciej W. Rozycki
2025-12-01 16:49                 ` Guinevere Larsen
2025-11-07  7:46   ` Eli Zaretskii
2025-11-07 13:41     ` Guinevere Larsen
2025-11-07 14:23       ` Eli Zaretskii
2025-11-08  2:25       ` Maciej W. Rozycki
2025-11-27 20:01         ` Guinevere Larsen
2025-11-28  9:20           ` Maciej W. Rozycki
2025-11-06 19:45 ` [PATCH 2/2] gdb: add warning when no native target is available Guinevere Larsen
2025-11-07  7:48   ` Eli Zaretskii
2025-11-07 13:24     ` Guinevere Larsen
2025-11-07 14:21       ` Eli Zaretskii
2025-11-27 20:15         ` Guinevere Larsen

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=alpine.DEB.2.21.2511271954290.36486@angie.orcam.me.uk \
    --to=macro@orcam.me.uk \
    --cc=gdb-patches@sourceware.org \
    --cc=guinevere@redhat.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