public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Robert Lipe <robertl@dgii.com>
To: egcs@cygnus.com
Subject: Re: Dwarf 1 or 2?
Date: Sat, 13 Dec 1997 13:07:00 -0000	[thread overview]
Message-ID: <19971213013237.09865@dgii.com> (raw)
In-Reply-To: <199712130128.RAA28826@kankakee.wrs.com>

Hi, Mike.

> 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

I certainly have no preferences or really even any useful information,
but in case you're compiling a list, the currently shipping SCO native
x86 stuff uses Dwarf 1 for ELF.   The new tools due to ship Real Soon 
Now (this is public knowledge, not an NDA violation) will generate 
Dwarf 2.   This would be their "Universal Development Kit" which hosts
on OpenServer, Unixware 2, or Unixware 7 (a.k.a. SVR5) and generates
binaries that will run on any of the three, obvious exceptions noted.

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

I'd like to hear the results of your survey.   I've been building
our embedded MIPS --wiht-stabs becuase GDB wouldn't play nice with
G++ any other way.   I have no compelling reason to change, but I 
always like having more options! :-)

Later,
RJL

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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-12-12 17:28 Mike Stump
1997-12-13 13:07 ` Robert Lipe [this message]
     [not found] <199712130128.RAA28826.cygnus.egcs@kankakee.wrs.com>
1997-12-12 18:04 ` Jason Merrill
1997-12-13 15:51 meissner

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=19971213013237.09865@dgii.com \
    --to=robertl@dgii.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).