From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tom@tromey.com>
Cc: pedro@palves.net, gdb-patches@sourceware.org
Subject: Re: [RFC] Deprecate stabs
Date: Wed, 30 Aug 2023 20:58:23 +0300 [thread overview]
Message-ID: <83ledsfm4g.fsf@gnu.org> (raw)
In-Reply-To: <87sf802zhi.fsf@tromey.com> (message from Tom Tromey on Wed, 30 Aug 2023 11:48:09 -0600)
> From: Tom Tromey <tom@tromey.com>
> Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
> Date: Wed, 30 Aug 2023 11:48:09 -0600
>
> Pedro> My position with stabs for years had been that, as long as GCC needs it for some ports,
> Pedro> we should keep it. Since GCC has since removed support for stabs, I think we're now
> Pedro> free to remove it too.
>
> Pedro> I think we should mark stabs deprecated for GDB 14. We can discuss more when to actually
> Pedro> remove it, but IMO, the sooner we mark it deprecated, the sooner people will be aware of our
> Pedro> intentions. FWIW, I do support removing it in GDB 15.
>
> It's maybe a little late for 14/15 now.
>
> I'm thinking I will send email to gdb@ and push the NEWS patch after the
> 14 branch is made. That is, deprecate in 15 and remove in 16.
>
> I have also been wondering if some of the other debug formats are still
> relevant. My suspicion is that they are long since obsolete.
Not obsolete, broken. They simply don't work, and for quite some
time. The few platforms which still need them cannot use the newer
GDB versions.
For example, the DJGPP (a.k.a. "go32") port of Emacs still uses the
COFF debug info, and the latest GDB version that can be used to debug
it is GDB 7.2. Any newer version simply cannot debug the program, and
either crashes or fails to start the debuggee and take control when
breakpoints are hit.
next prev parent reply other threads:[~2023-08-30 17:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 17:41 Tom Tromey
2023-01-19 18:00 ` Eli Zaretskii
2023-01-20 12:48 ` Mark Wielaard
2023-01-20 13:47 ` Eli Zaretskii
2023-02-11 2:26 ` Tom Tromey
2023-02-11 8:29 ` Eli Zaretskii
2023-02-14 16:36 ` Simon Marchi
2023-02-12 12:53 ` Mark Wielaard
2023-07-06 17:44 ` Pedro Alves
2023-08-30 17:48 ` Tom Tromey
2023-08-30 17:58 ` Eli Zaretskii [this message]
2023-08-30 19:15 ` Kevin Buettner
2023-08-30 20:47 ` John Baldwin
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=83ledsfm4g.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@palves.net \
--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).