From: David Carlton <carlton@math.stanford.edu>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: drow@mvista.com, gdb@sources.redhat.com
Subject: Re: Namespaces with gcc v3 stabs+?
Date: Fri, 06 Dec 2002 17:27:00 -0000 [thread overview]
Message-ID: <ro165u6aa9o.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <200212062105.gB6L5sH05223@duracef.shout.net>
On Fri, 6 Dec 2002 15:05:54 -0600, Michael Elizabeth Chastain <mec@shout.net> said:
> David Carlton writes:
>> What systems are there that GCC supports for which stabs+ can be
>> used but DWARF 2 can't? How important are they? Who's supporting
>> them? Are there other more modern debug formats that really should
>> be used on those systems in place of stabs?
> If the user builds gcc with "--with-stabs", gcc prefers dbx (the gcc
> name for stabs). Besides that, there are about 90 configurations
> which default to dbx, most of them without dwarf2 support. Darwin
> and Cygwin are the big ones, with some arm configurations in there.
Thanks for the list. And Darwin apparently supports DWARF 2. I'm not
suprised Cygwin is a sticky one, though, now that you mention it.
It seems to me that, for now, it wouldn't be a great idea to convince
GCC to generate a fancy version of stabs, then, until somebody appears
who's particularly motivated to deal with the issues that arise. So I
agree with your planned course of action.
David Carlton
carlton@math.stanford.edu
next prev parent reply other threads:[~2002-12-07 1:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-06 13:06 Michael Elizabeth Chastain
2002-12-06 17:27 ` David Carlton [this message]
2002-12-07 6:49 ` Stan Shebs
2002-12-09 10:59 ` David Carlton
2002-12-06 17:58 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2002-12-06 19:48 Michael Elizabeth Chastain
2002-12-05 18:06 Michael Elizabeth Chastain
2002-12-05 16:31 Michael Elizabeth Chastain
2002-12-05 17:14 ` Daniel Jacobowitz
2002-12-06 11:25 ` David Carlton
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=ro165u6aa9o.fsf@jackfruit.Stanford.EDU \
--to=carlton@math.stanford.edu \
--cc=drow@mvista.com \
--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