From: Daniel Jacobowitz <drow@mvista.com>
To: David Carlton <carlton@math.stanford.edu>
Cc: gdb <gdb@sources.redhat.com>, Michael Elizabeth Chastain <mec@shout.net>
Subject: Re: GCC, stabs, mangled names
Date: Tue, 11 Mar 2003 01:24:00 -0000 [thread overview]
Message-ID: <20030311012413.GA22236@nevyn.them.org> (raw)
In-Reply-To: <ro1r89esnq7.fsf@jackfruit.Stanford.EDU>
On Mon, Mar 10, 2003 at 05:20:32PM -0800, David Carlton wrote:
> On Mon, 10 Mar 2003 19:56:56 -0500, Daniel Jacobowitz <drow@mvista.com> said:
>
> > It's unclear what the right thing to do is. Stabs is underspecified
> > (and underimplemented too). Someone needs to decide what would be
> > useful.
>
> I compared this with 2.95.3, and it seems that GCC switched from only
> using mangled names to only using demangled names. If we can't have
> both, it seems to me that only having mangled names is more useful.
>
> Did anybody from the GDB side ask them to switch the output that they
> produced? If so, what was the rationale?
FYI, my position on stabs has crystalized over time: I don't care, use
DWARF-2. Even on Solaris if you use the GNU tools I believe DWARF-2 is
available as an option. If someone hits a platform that they care
about where this isn't an option, and they want to make the stabs
support work again, then we can deal with it - only then.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-03-11 1:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-11 0:53 David Carlton
2003-03-11 0:57 ` Daniel Jacobowitz
2003-03-11 1:20 ` David Carlton
2003-03-11 1:24 ` Daniel Jacobowitz [this message]
2003-03-11 5:55 Michael Elizabeth Chastain
2003-03-11 17:06 ` David Carlton
2003-03-11 6:07 Michael Elizabeth Chastain
2003-03-11 20:33 ` David Carlton
2003-03-11 17:24 Michael Elizabeth Chastain
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=20030311012413.GA22236@nevyn.them.org \
--to=drow@mvista.com \
--cc=carlton@math.stanford.edu \
--cc=gdb@sources.redhat.com \
--cc=mec@shout.net \
/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