Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Guinevere Larsen <guinevere@redhat.com>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/2] gdb: introduce command "info architecture"
Date: Fri, 7 Nov 2025 10:10:32 -0300	[thread overview]
Message-ID: <b4886bd1-a065-4198-af3c-02e7721821ec@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2511062316450.25436@angie.orcam.me.uk>

On 11/6/25 8:24 PM, Maciej W. Rozycki wrote:
> On Thu, 6 Nov 2025, Guinevere Larsen wrote:
>
>> 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.
>   Umm, doesn't `set architecture' do the right job?
>
> (gdb) set architecture
> Requires an argument. Valid arguments are ARC600, A6, ARC601, ARC700, A7, ARCv2, EM, HS, arm, armv2, armv2a, armv3, armv3m, armv4, armv4t, armv5, armv5t, armv5te, xscale, iwmmxt, iwmmxt2, armv5tej, armv6, armv6kz, armv6t2, armv6k, armv7, armv6-m, armv6s-m, armv7e-m, armv8-a, armv8-r, armv8-m.base, armv8-m.main, armv8.1-m.main, armv9-a, arm_any, avr, avr:1, avr:2, avr:25, avr:3, avr:31, avr:35, avr:4, avr:5, avr:51, avr:6, avr:100, avr:101, avr:102, avr:103, avr:104, avr:105, avr:106, avr:107, bfin, cris, crisv32, cris:common_v10_v32, csky, csky:ck510, csky:ck610, csky:ck801, csky:ck802, csky:ck803, csky:ck807, csky:ck810, csky:ck860, csky:any, frv, tomcat, simple, fr550, fr500, fr450, fr400, fr300, ft32, ft32b, h8300, h8300h, h8300s, h8300hn, h8300sn, h8300sx, h8300sxn, hppa1.0, i386, i386:x86-64, i386:x64-32, i8086, i386:intel, i386:x86-64:intel, i386:x64-32:intel, iq2000, iq10, lm32, m16c, m32c, m32r, m32rx, m32r2, m68hc11, m68hc12, m68hc12:HCS12, m68k, m68k:68000, m68k:68008, m68k
>   :68010, m68k:68020, m68k:68030, m68k:68040, m68k:68060, m68k:cpu32, m68k:fido, m68k:isa-a:nodiv, m68k:isa-a, m68k:isa-a:mac, m68k:isa-a:emac, m68k:isa-aplus, m68k:isa-aplus:mac, m68k:isa-aplus:emac, m68k:isa-b:nousp, m68k:isa-b:nousp:mac, m68k:isa-b:nousp:emac, m68k:isa-b, m68k:isa-b:mac, m68k:isa-b:emac, m68k:isa-b:float, m68k:isa-b:float:mac, m68k:isa-b:float:emac, m68k:isa-c, m68k:isa-c:mac, m68k:isa-c:emac, m68k:isa-c:nodiv, m68k:isa-c:nodiv:mac, m68k:isa-c:nodiv:emac, m68k:5200, m68k:5206e, m68k:5307, m68k:5407, m68k:528x, m68k:521x, m68k:5249, m68k:547x, m68k:548x, m68k:cfv4e, mep, h1, c5, MicroBlaze, mn10300, am33, am33-2, moxie, msp:14, MSP430, MSP430x11x1, MSP430x12, MSP430x13, MSP430x14, MSP430x15, MSP430x16, MSP430x20, MSP430x21, MSP430x22, MSP430x23, MSP430x24, MSP430x26, MSP430x31, MSP430x32, MSP430x33, MSP430x41, MSP430x42, MSP430x43, MSP430x44, MSP430x46, MSP430x47, MSP430x54, MSP430X, n1, n1h, n1h_v2, n1h_v3, n1h_v3m, or1k, or1knd, rl78, rs6000:6000, rs6000:rs1, rs60
>   00:rsc, rs6000:rs2, powerpc:common, powerpc:common64, powerpc:603, powerpc:EC603e, powerpc:604, powerpc:403, powerpc:601, powerpc:620, powerpc:630, powerpc:a35, powerpc:rs64ii, powerpc:rs64iii, powerpc:7400, powerpc:e500, powerpc:e500mc, powerpc:e500mc64, powerpc:MPC8XX, powerpc:750, powerpc:titan, powerpc:vle, powerpc:e5500, powerpc:e6500, rx, rx:v2, rx:v3, s12z, s390:31-bit, s390:64-bit, sh, sh2, sh2e, sh-dsp, sh3, sh3-nommu, sh3-dsp, sh3e, sh4, sh4a, sh4al-dsp, sh4-nofpu, sh4-nommu-nofpu, sh4a-nofpu, sh2a, sh2a-nofpu, sh2a-nofpu-or-sh4-nommu-nofpu, sh2a-nofpu-or-sh3-nommu, sh2a-or-sh4, sh2a-or-sh3e, sparc, sparc:sparclet, sparc:sparclite, sparc:v8plus, sparc:v8plusa, sparc:sparclite_le, sparc:v9, sparc:v9a, sparc:v8plusb, sparc:v9b, sparc:v8plusc, sparc:v9c, sparc:v8plusd, sparc:v9d, sparc:v8pluse, sparc:v9e, sparc:v8plusv, sparc:v9v, sparc:v8plusm, sparc:v9m, sparc:v8plusm8, sparc:v9m8, tic6x, v850:old-gcc-abi, v850e3v5:old-gcc-abi, v850e2v4:old-gcc-abi, v850e2v3:old-gcc-abi, v8
>   50e2:old-gcc-abi, v850e1:old-gcc-abi, v850e:old-gcc-abi, v850:rh850, v850e3v5, v850e2v4, v850e2v3, v850e2, v850e1, v850e, v850-rh850, vax, xstormy16, xtensa, z80, z80-strict, z80-full, r800, gbz80, z180, z80n, ez80-z80, ez80-adl, aarch64, aarch64:llp64, aarch64:ilp32, aarch64:armv8-r, alpha, alpha:ev4, alpha:ev5, alpha:ev6, bpf, xbpf, ia64-elf64, ia64-elf32, Loongarch64, Loongarch32, mips, mips:3000, mips:3900, mips:4000, mips:4010, mips:4100, mips:4111, mips:4120, mips:4300, mips:4400, mips:4600, mips:4650, mips:5000, mips:5400, mips:5500, mips:5900, mips:6000, mips:7000, mips:8000, mips:9000, mips:10000, mips:12000, mips:14000, mips:16000, mips:16, mips:mips5, mips:isa32, mips:isa32r2, mips:isa32r3, mips:isa32r5, mips:isa32r6, mips:isa64, mips:isa64r2, mips:isa64r3, mips:isa64r5, mips:isa64r6, mips:sb1, mips:loongson_2e, mips:loongson_2f, mips:gs464, mips:gs464e, mips:gs264e, mips:octeon, mips:octeon+, mips:octeon2, mips:octeon3, mips:xlr, mips:interaptiv-mr2, mips:allegrex, mips:
>   micromips, riscv, riscv:rv64, riscv:rv32, tilegx, tilegx32, auto.
> (gdb)
>
> 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.

This is mostly inspired by the second patch, where the error tells you 
how to get a list of supported CPUs, and I think that having a hint that 
uses an incorrect command is not great.

>
>    Maciej
>
>

-- 
Cheers,
Guinevere Larsen
It/she


  reply	other threads:[~2025-11-07 13:11 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 [this message]
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
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=b4886bd1-a065-4198-af3c-02e7721821ec@redhat.com \
    --to=guinevere@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=macro@orcam.me.uk \
    /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