public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug symtab/28900] GDB crash on loading symbols form openbios binary
Date: Fri, 18 Feb 2022 16:52:09 +0000 [thread overview]
Message-ID: <bug-28900-4717-pn2vMsaYBn@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28900-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28900
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tromey at sourceware dot org
--- Comment #7 from Tom Tromey <tromey at sourceware dot org> ---
(In reply to Glenn Washburn from comment #6)
> I also don't expect stabs support to be
> removed anytime soon, as there's always people on legacy software and
> they'll probably want to keep what's there.
I think the issue in gdb is that there just aren't really stabs
experts around any more. I've worked on gdb "forever" (like > 10 years)
and never had to touch stabs.
So, while we'd probably accept a fix for this, if it seemed clean somehow
(I really don't know how I'd make that assessment given the minimal
knowledge I have...), most likely nobody is going to pick this up.
Also, worth noting, GCC is finally going to get rid of stabs output:
https://gcc.gnu.org/gcc-12/changes.html
So perhaps fixing the kernel is the best outcome here.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-02-18 16:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 22:02 [Bug symtab/28900] New: " development at efficientek dot com
2022-02-17 0:43 ` [Bug symtab/28900] " simark at simark dot ca
2022-02-17 16:17 ` development at efficientek dot com
2022-02-17 16:26 ` simark at simark dot ca
2022-02-17 16:28 ` simark at simark dot ca
2022-02-17 16:47 ` schwab@linux-m68k.org
2022-02-17 18:44 ` development at efficientek dot com
2022-02-18 16:52 ` tromey at sourceware dot org [this message]
2022-02-18 16:57 ` simark at simark dot ca
2022-02-19 19:53 ` aburgess at redhat dot com
2022-02-21 11:49 ` cvs-commit at gcc dot gnu.org
2022-02-21 12:06 ` aburgess at redhat dot com
2022-04-29 19:54 ` tromey at sourceware dot org
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=bug-28900-4717-pn2vMsaYBn@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).