From: Jason Merrill <jason@cygnus.com>
To: egcs@cygnus.com
Subject: Re: Dwarf 1 or 2?
Date: Fri, 12 Dec 1997 18:04:00 -0000 [thread overview]
Message-ID: <u990tq0zi6.fsf@yorick.cygnus.com> (raw)
In-Reply-To: <199712130128.RAA28826.cygnus.egcs@kankakee.wrs.com>
>>>>> Mike Stump <mrs@wrs.com> writes:
> If one was going to switch to dwarf, what would be the better dwarf to
> pick? Dwarf 1, or 2? I ask because quite a few different groups
> (processor abi groups) seem to picking up dwarf 1, and no one seems to
> be behind 2 (except Linux and sgi).
Dwarf 2 is clearly technically superior. Dwarf 1 has more existing
implementations, and therefore more political clout.
> I'm interested in user experiences with dwarf 2 systems, (sparc v9
> linux, iris6) with gdb and how well it holds up in relationship to
> stabs.
One important win of dwarf2 over stabs on x86 linux is that it allows for
debugging of frame-pointerless code. In theory, that is; gdb doesn't
grok the frame unwind info yet, but all the necessary info is there.
Jason
next parent reply other threads:[~1997-12-12 18:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199712130128.RAA28826.cygnus.egcs@kankakee.wrs.com>
1997-12-12 18:04 ` Jason Merrill [this message]
1997-12-13 15:51 meissner
-- strict thread matches above, loose matches on Subject: below --
1997-12-12 17:28 Mike Stump
1997-12-13 13:07 ` Robert Lipe
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=u990tq0zi6.fsf@yorick.cygnus.com \
--to=jason@cygnus.com \
--cc=egcs@cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).