diff options
author | Guinevere Larsen <guinevere@redhat.com> | 2025-01-13 14:04:04 -0300 |
---|---|---|
committer | Guinevere Larsen <guinevere@redhat.com> | 2025-02-10 15:31:03 -0300 |
commit | f35bb15bed4ef1179f6c54654a590c825e53c3dc (patch) | |
tree | cc8dc4ceea4d7d251ad6cf38213413da587f35ae /ld/testsuite/ld-arm/unwind-rel2.s | |
parent | 13ab441fb40abffd9bb2a2ac32e1c69cba6c3198 (diff) | |
download | gdb-master.zip gdb-master.tar.gz gdb-master.tar.bz2 |
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.
Finally, deprecating and removing stabs will make a.out/dbx inferiors be
essentially unsupported, as the only debuginfo GDB supports for those
formats is stabs, meaning users would only have assembly-level debugging
for that format. With that in mind, this commit deprecates the a.out/dbx
format as well.
[1] https://inbox.sourceware.org/gdb-patches/20230119174156.654402-1-tom@tromey.com/
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=31210
Approved-By: Tom Tromey <tom@tromey.com>
Diffstat (limited to 'ld/testsuite/ld-arm/unwind-rel2.s')
0 files changed, 0 insertions, 0 deletions