From: Tom Tromey <tom@tromey.com>
To: Guinevere Larsen <guinevere@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb, configure: Add disable-formats option for configure
Date: Thu, 26 Sep 2024 13:18:58 -0600 [thread overview]
Message-ID: <87ldzei5p9.fsf@tromey.com> (raw)
In-Reply-To: <20240925175340.1850969-1-guinevere@redhat.com> (Guinevere Larsen's message of "Wed, 25 Sep 2024 14:53:40 -0300")
>>>>> Guinevere Larsen <guinevere@redhat.com> writes:
> Ideally we'd like to be able to disable even those formats, in case a
> user wants to build GDB only to examine remote files for example, but
> the current infrastructure for the file format readers doesn't allow
> us to do it.
The goal seems totally fine to me.
> +enable-formats=[FORMAT,]...
I think this option name is too generic.
> +# If all targets were requested, this is all formats that should accompany
> +# them.
> +all_target_formats="elf xcoff mips coff"
I think it would be nicer if the full list only had to be written in one
spot. Right now it seems like it's both here and in the makefile? viz:
+# All files that relate to GDB's ability to read debug information.
+# Used with --enable-formats=all.
+ALL_FORMAT_OBS = \
I'd written some more stuff here about maybe just following BFD's lead.
But looking at my "minimal" build tree, I see a native Linux gdb seems
to have COFF and other junk in BFD, so following BFD doesn't seem really
possible.
Tom
next prev parent reply other threads:[~2024-09-26 19:19 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-25 17:53 Guinevere Larsen
2024-09-26 5:49 ` Eli Zaretskii
2024-09-26 18:16 ` Guinevere Larsen
2024-09-26 18:35 ` Eli Zaretskii
2024-09-26 21:03 ` Guinevere Larsen
2024-09-27 6:05 ` Eli Zaretskii
2024-10-02 13:25 ` Andrew Burgess
2024-10-02 14:15 ` Eli Zaretskii
2024-10-04 14:26 ` Andrew Burgess
2024-10-04 14:45 ` Eli Zaretskii
2024-10-07 18:30 ` Guinevere Larsen
2024-10-07 19:17 ` Eli Zaretskii
2024-10-07 19:58 ` Guinevere Larsen
2024-10-08 11:44 ` Eli Zaretskii
2024-10-08 13:03 ` Guinevere Larsen
2024-10-08 13:21 ` Eli Zaretskii
2024-10-10 14:45 ` Guinevere Larsen
2024-10-10 16:10 ` Andrew Burgess
2024-09-26 19:18 ` Tom Tromey [this message]
2024-09-26 19:49 ` Guinevere Larsen
2024-09-27 18:01 ` Tom Tromey
2024-10-02 13:56 ` Andrew Burgess
2024-10-02 20:37 ` Guinevere Larsen
2024-10-03 10:15 ` Andrew Burgess
2024-10-04 14:49 ` Andrew Burgess
2024-10-10 20:18 ` Guinevere Larsen
2024-10-16 10:50 ` Andrew Burgess
2024-10-16 21:00 ` Guinevere Larsen
2024-10-17 19:43 ` Tom Tromey
2024-10-17 19:48 ` 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=87ldzei5p9.fsf@tromey.com \
--to=tom@tromey.com \
--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