From: Keith Seitz <keiths@redhat.com>
To: Tom Tromey <tom@tromey.com>,
Keith Seitz via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Verify COFF symbol stringtab offset
Date: Fri, 25 Aug 2023 12:46:48 -0700 [thread overview]
Message-ID: <3b0896a6-04d4-4c7c-ac32-9ae78acdb66c@redhat.com> (raw)
In-Reply-To: <877cpnw04v.fsf@tromey.com>
On 8/22/23 08:46, Tom Tromey wrote:
>>>>>> "Keith" == Keith Seitz via Gdb-patches <gdb-patches@sourceware.org> writes:
>
> Keith> Unfortunately, I haven't any idea how else to test this patch since
> Keith> COFF is not very common anymore. GCC removed support for it five
> Keith> years ago with GCC 8.
>
> If it is really that dead, then -- like stabs -- I'd like to remove it.
> These dead formats just make it harder to improve gdb while not
> providing value to any user.
>
> Actually with the advent of fuzzers, this code now has negative value,
> because it wastes time coming up with patches to fix bugs in code no one
> uses.
I was tempted to suggest either removing it or at least adding a --disable-reader-coff
option to disable the code, but I could not convince myself that there
wouldn't be relatively widespread disagreement.
If you feel there's a chance, let me know if you like either of these approaches,
and I will get it on my TODO list.
> Hmm, I should probably go reply on the stabs thread.
>
> Anyway, this is ok.
Thank you again for your quick review! Pushed 58abdf88782.
Keith
next prev parent reply other threads:[~2023-08-25 19:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 15:23 Keith Seitz
2023-08-22 15:46 ` Tom Tromey
2023-08-25 19:46 ` Keith Seitz [this message]
2023-08-28 16:53 ` Tom Tromey
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=3b0896a6-04d4-4c7c-ac32-9ae78acdb66c@redhat.com \
--to=keiths@redhat.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).