Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Guinevere Larsen <guinevere@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/2] gdb: introduce command "info architecture"
Date: Fri, 07 Nov 2025 09:46:41 +0200	[thread overview]
Message-ID: <865xbmb7z2.fsf@gnu.org> (raw)
In-Reply-To: <20251106194514.1857177-2-guinevere@redhat.com> (message from Guinevere Larsen on Thu, 6 Nov 2025 16:45:13 -0300)

> From: Guinevere Larsen <guinevere@redhat.com>
> Cc: Guinevere Larsen <guinevere@redhat.com>
> Date: Thu,  6 Nov 2025 16:45:13 -0300
> 
> There is no convenient way to tell a user how to check which
> architectures are supported by their build of GDB.  This hasn't really
> been a problem, but now that GDB isn't ported to Apple's new CPU
> architectures, a user could run into a situation where they're trying to
> debug an unsupported CPU.
> 
> This commit adds a way to list supported architectures, and filter them
> using a regular expression.  No test is added because I couldn't think
> of a good way to verify functionality when we can't control the
> configure line.
> ---
>  gdb/NEWS            |  4 ++++
>  gdb/arch-utils.c    | 28 ++++++++++++++++++++++++++++
>  gdb/doc/gdb.texinfo |  5 +++++
>  3 files changed, 37 insertions(+)

Thanks.  The documentation parts are okay (with one nit, see below),
but I'm struggling to understand what you mean by "CPU
microarchitectures".  And without examples, I cannot even guess.
Would it be possible to expand on that in the manual, or at least
provide a could of examples of what the output will look like?

> +@item info architectures
> +@item info architectures @var{regexp}
> +List architectures supported by GDB. If @var{regexp} is provided, filter
                                      ^^
Two spaces there.

Reviewed-By: Eli Zaretskii <eliz@gnu.org>

  parent reply	other threads:[~2025-11-07  7:47 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
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 [this message]
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=865xbmb7z2.fsf@gnu.org \
    --to=eliz@gnu.org \
    --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