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/31210] [gdb, symtab] Deprecate stabs
Date: Wed, 10 Jan 2024 18:23:02 +0000	[thread overview]
Message-ID: <bug-31210-4717-FZvKKkziI8@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31210-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=31210

--- Comment #5 from Tom Tromey <tromey at sourceware dot org> ---
(In reply to Tom de Vries from comment #1)
> FWIW, one related idea I had: if there was a tool to translate stabs to
> dwarf, either external or in the form of a library, then there would be no
> need for gdb, or indeed any other tool supporting dwarf to continue
> supporting stabs natively.  
> 
> My guess is that such a tool could be feasible given that dwarf is generally
> considered the more expressive format.

Definitely feasible.  I think the main problem is that probably no-one
knows or cares enough to write it.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      parent reply	other threads:[~2024-01-10 18:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-04 12:27 [Bug symtab/31210] New: " vries at gcc dot gnu.org
2024-01-04 12:34 ` [Bug symtab/31210] " vries at gcc dot gnu.org
2024-01-05 10:23 ` ssbssa at sourceware dot org
2024-01-08 12:08 ` vries at gcc dot gnu.org
2024-01-08 23:22 ` tromey at sourceware dot org
2024-01-09 10:17 ` vries at gcc dot gnu.org
2024-01-10 18:22 ` tromey at sourceware dot org
2024-01-10 18:23 ` tromey at sourceware dot org [this message]

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-31210-4717-FZvKKkziI8@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).