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: Fri, 7 Nov 2025 15:51:50 +0000 (GMT)	[thread overview]
Message-ID: <alpine.DEB.2.21.2511071528570.25436@angie.orcam.me.uk> (raw)
In-Reply-To: <b4886bd1-a065-4198-af3c-02e7721821ec@redhat.com>

On Fri, 7 Nov 2025, Guinevere Larsen wrote:

> > Or am I missing something?  Of course adding filtering might be useful,
> > especially if the list so large as in my quoted example, but the change
> > description suggests there's no listing facility available.
> 
> Well, I wouldn't say we have a listing facility. using Set Architecture
> without an argument may list them, but that is an error message, rather than a
> command to do that, which is why I don't think it is a convenient way to tell
> a user to check for support. You could achieve the same if you asked for
> completion, but again, not a "listing facility" in the sense of telling a user
> to check.

 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, 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.

 BTW is there a way to globally disable styling by default?  I find it 
irritating (it distracts me and hurts my eyes) as I do having to type:

(gdb) set style enabled off

every time.  Placing the command in $HOME/.config/gdb/gdbinit or 
$HOME/.gdbinit does nothing, the welcome message is still a disturbing 
mixture of colours.

  Maciej

  reply	other threads:[~2025-11-07 15:52 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 [this message]
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
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.2511071528570.25436@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