From: Guinevere Larsen <guinevere@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/1] gdb: Deprecate stabs debug info
Date: Mon, 27 Jan 2025 09:08:15 -0300 [thread overview]
Message-ID: <592a9fcc-90b4-467b-bc4d-3f223797857a@redhat.com> (raw)
In-Reply-To: <20250113181359.1286957-1-guinevere@redhat.com>
Ping.
I'm planning on pushing this next monday, so if anyone has negative
feedback on this, speak now or forever hold your peace.
--
Cheers,
Guinevere Larsen
She/Her/Hers
On 1/13/25 3:13 PM, Guinevere Larsen wrote:
> GCC has deprecated stabs generation in GCC 12 and entirely removed it in
> GCC 13, which was released in April 2023. At the time it was proposed
> that GDB deprecate stabs as well, but the decision was to support it a
> bit longer. With this patch, it'll be deprecated on GDB 17, and removed
> on GDB 18, which following the current cadence, will be released early
> 2026, meaning we will have supported stabs for nearly 3 years longer
> than GCC, which I think is reasonable.
>
> As pointed out in the previous discussion on this topic[1], there are
> several existing issues on the code, and none of the current maintainers
> knows how to fix it. Unless someone steps up to fix this before the
> removal on GDB 18, I don't see why we should keep this old code that
> breaks all conventions of modern debuginfo readers and doesn't even
> work, instead of being able to further advance adjacent code.
>
> [1] https://inbox.sourceware.org/gdb-patches/20230119174156.654402-1-tom@tromey.com/
> ---
> gdb/NEWS | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/gdb/NEWS b/gdb/NEWS
> index f454846646e..685ecefbe1c 100644
> --- a/gdb/NEWS
> +++ b/gdb/NEWS
> @@ -44,6 +44,9 @@ maintenance check symtabs
> ** New constant PARAM_COLOR represents color type of a value
> of a <gdb:parameter> object. Parameter's value is <gdb::color> instance.
>
> +* Support for stabs debugging format is deprecates, and will be
> + removed in GDB 18.
> +
> *** Changes in GDB 16
>
> * Support for Nios II targets has been removed as this architecture
next prev parent reply other threads:[~2025-01-27 12:09 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
2025-01-14 17:58 ` Andrew Burgess
2025-01-20 5:22 ` Tom de Vries
2025-01-27 12:08 ` Guinevere Larsen [this message]
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=592a9fcc-90b4-467b-bc4d-3f223797857a@redhat.com \
--to=guinevere@redhat.com \
--cc=gdb-patches@sourceware.org \
/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