public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: meissner@cygnus.com
To: egcs@cygnus.com
Subject: Re:  Dwarf 1 or 2?
Date: Sat, 13 Dec 1997 15:51:00 -0000	[thread overview]
Message-ID: <199712132351.SAA12753@tweedledumb.cygnus.com> (raw)

| > The dwarf 2 spec can be found in
| 
| >   ftp://sgigate.sgi.com/pub/dwarf
| 
| > if anyone's interested in doing that work.
| 
| 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 a better debugging language.  The ABI groups are going with Dwarf 1
because it is a standard, and the Dwarf 2 group got caught in the changes in
the System V world and went under before having it become a standard.  The
PowerPC ABI group for instance has a bunch of changes to dwarf 1 to support C++
better.  From a practical point of view, the dwarf-2 code in gcc (and possibly
gdb) is still new enough that it may still have bugs.

| 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.
| 

             reply	other threads:[~1997-12-13 15:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-12-13 15:51 meissner [this message]
     [not found] <199712130128.RAA28826.cygnus.egcs@kankakee.wrs.com>
1997-12-12 18:04 ` Jason Merrill
  -- 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=199712132351.SAA12753@tweedledumb.cygnus.com \
    --to=meissner@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).