From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: RFA: fix for GDB C++ STABS problem
Date: Wed, 01 May 2002 18:29:00 -0000 [thread overview]
Message-ID: <20020501212939.A15160@nevyn.them.org> (raw)
In-Reply-To: <20020502012250.3FAD65EA11@zwingli.cygnus.com>
On Wed, May 01, 2002 at 08:22:50PM -0500, Jim Blandy wrote:
>
> Here's a fix for the GDB C++ STABS problem I just posted a test case
> for. This prevents `read_struct_type' from scribbling over an
> existing definition, but it doesn't prevent `cleanup_undefined_types'
> from producing bogus cv chains. That's the next patch coming.
>
> The real fix, of course, is to switch to Dwarf 2.
Amen! Thanks for tracking this down.
We could also start supporting the current Sun STABS spec, and then
make GCC emit it - it supports things like namespaces quite well. But
at that point, well, most ELF targets already default to DWARF-2 in GCC
3.1.
I'd rather just go forward with the namespace improvements we were
discussing and leave STABS to rot.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2002-05-02 1:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-01 18:23 Jim Blandy
2002-05-01 18:29 ` Daniel Jacobowitz [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=20020501212939.A15160@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@sources.redhat.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