From: Eli Zaretskii <eliz@delorie.com>
To: dan@cgsoftware.com
Cc: jtc@redback.com, gdb@sourceware.cygnus.com,
binutils@sourceware.cygnus.com
Subject: Re: stabs vs. dwarf-2 for C programs
Date: Thu, 12 Apr 2001 23:37:00 -0000 [thread overview]
Message-ID: <200104130637.CAA07371@delorie.com> (raw)
In-Reply-To: <m2y9t5y0ej.fsf@dynamic-addr-83-177.resnet.rochester.edu>
> From: Daniel Berlin <dan@cgsoftware.com>
> Date: 12 Apr 2001 22:54:44 -0400
>
> jtc@redback.com (J.T. Conklin) writes:
>
> > In general, are there any advantages for using dwarf-2 over
> > stabs debugging symbols for C (not C++) programs?
>
> Unless you want optimized code debugging, only space savings
> (theoretical, of course, right now. For C, anyway).
I _always_ debug optimized code (I think doing otherwise is not wise,
to put it gently). What are the advantages of dwarf2 for debugging
optimized C code?
next prev parent reply other threads:[~2001-04-12 23:37 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
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 [this message]
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=200104130637.CAA07371@delorie.com \
--to=eliz@delorie.com \
--cc=binutils@sourceware.cygnus.com \
--cc=dan@cgsoftware.com \
--cc=gdb@sourceware.cygnus.com \
--cc=jtc@redback.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