From: Tom Tromey <tom@tromey.com>
To: Guinevere Larsen <guinevere@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/1] gdb: Deprecate stabs debug info
Date: Tue, 14 Jan 2025 09:47:23 -0700 [thread overview]
Message-ID: <877c6xs5pg.fsf@tromey.com> (raw)
In-Reply-To: <20250113181359.1286957-1-guinevere@redhat.com> (Guinevere Larsen's message of "Mon, 13 Jan 2025 15:13:59 -0300")
>>>>> "Guinevere" == Guinevere Larsen <guinevere@redhat.com> writes:
Guinevere> As pointed out in the previous discussion on this topic[1], there are
Guinevere> several existing issues on the code, and none of the current maintainers
Guinevere> knows how to fix it. Unless someone steps up to fix this before the
Guinevere> removal on GDB 18, I don't see why we should keep this old code that
Guinevere> breaks all conventions of modern debuginfo readers and doesn't even
Guinevere> work, instead of being able to further advance adjacent code.
I completely agree.
I'm in favor of this patch but I think you should wait a little while in
case there are any objections.
Approved-By: Tom Tromey <tom@tromey.com>
Also please add this trailer:
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=31210
thanks,
Tom
next prev parent reply other threads:[~2025-01-14 16:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-13 18:13 Guinevere Larsen
2025-01-13 18:30 ` Eli Zaretskii
2025-01-13 19:01 ` Guinevere Larsen
2025-01-14 16:47 ` Tom Tromey [this message]
2025-01-14 17:58 ` Andrew Burgess
2025-01-20 5:22 ` Tom de Vries
2025-01-27 12:08 ` Guinevere Larsen
2025-01-27 18:47 ` [PATCH v2] " Guinevere Larsen
2025-01-27 19:24 ` Eli Zaretskii
2025-01-28 17:47 ` Tom Tromey
2025-01-28 19:23 ` Guinevere Larsen
2025-02-10 18:47 ` 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=877c6xs5pg.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