From: Christopher Faylor <cgf@redhat.com>
To: gdb@sources.redhat.com, binutils@sources.redhat.com
Subject: Re: stabs vs. dwarf-2 for C programs
Date: Thu, 12 Apr 2001 19:17:00 -0000 [thread overview]
Message-ID: <20010412221742.A22383@redhat.com> (raw)
In-Reply-To: <5mwv8pzgvt.fsf@jtc.redback.com>
On Thu, Apr 12, 2001 at 07:13:26PM -0700, J.T. Conklin wrote:
>In general, are there any advantages for using dwarf-2 over
>stabs debugging symbols for C (not C++) programs?
>
>I did a quick test of rebuilding our system with dwarf-2 debug
>symbols, and found that the image file grew from 35MB to 167MB
>and link times nearly quadrupled, so dwarf-2 isn't looking so
>good so far. If I had to guess, it looks like duplicate debug
>info (from headers, etc.) isn't being eliminated as is done
>for stabs.
Daniel Berlin contributed some duplicate debug elimination code to gcc
for Dwarf-2. It should be in the gcc 3.0 branch, if you are
adventurous.
There is an option to turn it on "-feliminate-dwarf2-dups". I don't
know if this is the default or not.
cgf
next prev parent reply other threads:[~2001-04-12 19:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-12 19:13 J.T. Conklin
2001-04-12 19:17 ` Christopher Faylor [this message]
2001-04-12 19:31 ` J.T. Conklin
2001-04-12 19:59 ` Daniel Berlin
2001-04-13 7:13 ` John Haller
2001-04-13 8:09 ` Daniel Berlin
2001-04-13 16:18 ` Ian Lance Taylor
2001-04-13 18:39 ` Daniel Berlin
2001-04-13 20:22 ` Ian Lance Taylor
2001-04-13 22:01 ` Daniel Berlin
2001-04-13 22:19 ` Ian Lance Taylor
2001-04-13 22:37 ` DJ Delorie
2001-04-13 23:31 ` Daniel Berlin
2001-04-13 23:47 ` Daniel Berlin
2001-04-13 23:51 ` Ian Lance Taylor
2001-04-13 22:56 ` Daniel Berlin
2001-04-13 23:40 ` Ian Lance Taylor
2001-04-13 23:55 ` Todd Whitesel
2001-04-12 19:55 ` Daniel Berlin
2001-04-12 23:37 ` Eli Zaretskii
2001-04-13 8:13 ` Daniel Berlin
2001-04-12 22:00 ` Geoff Keating
2001-04-12 22:37 ` Daniel Berlin
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=20010412221742.A22383@redhat.com \
--to=cgf@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=gdb@sources.redhat.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