Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Guinevere Larsen <guinevere@redhat.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org, Eli Zaretskii <eliz@gnu.org>
Subject: Re: [PATCH v7 1/1] gdb, configure: Add enable-binary-file-format option for configure
Date: Thu, 14 Aug 2025 13:23:35 -0300	[thread overview]
Message-ID: <b9020d3e-4d5e-43f5-bca1-832577780a84@redhat.com> (raw)
In-Reply-To: <87wm75nc8g.fsf@tromey.com>

On 8/14/25 12:39 PM, Tom Tromey wrote:
>>>>>> "Guinevere" == Guinevere Larsen <guinevere@redhat.com> writes:
> Guinevere> GDB has support for many binary file formats, some which might be very
> Guinevere> unlikely to be found in some situations (such as the XCOFF format in
> Guinevere> an x86 system). This commit introduces the option for a user to choose
> Guinevere> which formats GDB will support at build configuration time.
>
> I think you addressed all the review comments.
> This looks fine to me.
>
> Approved-By: Tom Tromey <tom@tromey.com>
Thank you! pushed!
>
> Guinevere> Mach-O and elf support are also dependent on BFD support being compiled
> Guinevere> in.  In case one of those was requested and BFD does not support them,
> Guinevere> the following error is emitted:
>
> I don't recall - was there a reason this isn't entirely BFD-centric?
> Like, some option to disable formats in BFD and then gdb would just
> adapt to this?

Mainly because it wouldn't work with the format of 
--enable-binary-file-format (I think anyway).

These attack surface patches were my first experience with autotools, so 
I wanted to make things as simple as possible while remaining consistent.

-- 
Cheers,
Guinevere Larsen
She/it


  reply	other threads:[~2025-08-14 16:24 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-07 11:58 [PATCH v3] gdb, configure: Add disable-formats " Guinevere Larsen
2025-03-07 12:09 ` Eli Zaretskii
2025-03-07 12:49   ` Guinevere Larsen
2025-03-07 13:03     ` Eli Zaretskii
2025-03-27 20:21 ` [PING][PATCH " Guinevere Larsen
2025-04-03 17:35 ` [PATCH " Tom Tromey
2025-04-07 17:48   ` Guinevere Larsen
2025-04-07 19:23     ` Tom Tromey
2025-04-08 13:47 ` [PATCH v4] " Guinevere Larsen
2025-04-08 14:06   ` Andreas Schwab
2025-04-08 14:24     ` Guinevere Larsen
2025-04-08 14:44       ` Andreas Schwab
2025-05-26 17:11   ` [PATCH v5 1/1] " Guinevere Larsen
2025-07-07 20:16     ` [PATCH v6] " Guinevere Larsen
2025-07-31 18:42       ` [PING][PATCH " Guinevere Larsen
2025-08-05 16:03       ` [PATCH " Simon Marchi
2025-08-05 19:06         ` Eli Zaretskii
2025-08-05 19:36           ` Simon Marchi
2025-08-05 20:07         ` Guinevere Larsen
2025-08-06 13:53           ` Guinevere Larsen
2025-08-06 14:17       ` [PATCH v7 1/1] gdb, configure: Add enable-binary-file-format " Guinevere Larsen
2025-08-14 15:39         ` Tom Tromey
2025-08-14 16:23           ` Guinevere Larsen [this message]
2025-05-27 11:32 ` [PATCH v3] gdb, configure: Add disable-formats " Pedro Alves
2025-05-27 16:26   ` 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=b9020d3e-4d5e-43f5-bca1-832577780a84@redhat.com \
    --to=guinevere@redhat.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.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