Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: dtaylor@emc.com
Cc: drow@false.org, jr.peulve@wanadoo.fr, gdb@sources.redhat.com
Subject: Re: stabs vs dwarf (was: Re: Wrong address for static function in linux module )
Date: Thu, 13 Apr 2006 07:02:00 -0000	[thread overview]
Message-ID: <200604121824.k3CIOuJm000173@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <200604121538.k3CFc9Mm005686@mailhub.lss.emc.com> (message from 	David Taylor on Wed, 12 Apr 2006 11:38:09 -0400)

> Date: Wed, 12 Apr 2006 11:38:09 -0400
> From: David Taylor <dtaylor@emc.com>
> 
> A full build tree (build products only, no sources) is 8.7 GB with
> STABS, but 24.6 GB when built with -gdwarf-2 -feliminate-dwarf2-dups.

You know if you compiled without debug information, your build tree
would be even smaller.  What matters is whether the debug info is
actually usable.  For unoptimized C code, stabs is probably fine.  But
for heavily optimized C++ code, it will be unusable.

Mark


  reply	other threads:[~2006-04-12 18:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-11 13:33 Wrong address for static function in linux module Jean-Rene Peulve
2006-04-11 13:38 ` Daniel Jacobowitz
2006-04-11 13:45   ` Jean-Rene Peulve
2006-04-11 13:55     ` Daniel Jacobowitz
2006-04-11 14:41       ` Jean-Rene Peulve
2006-04-11 15:05         ` Daniel Jacobowitz
2006-04-12 11:38           ` Jean-Rene Peulve
2006-04-12 16:36           ` stabs vs dwarf (was: Re: Wrong address for static function in linux module ) David Taylor
2006-04-13  7:02             ` Mark Kettenis [this message]
2006-04-13  8:26               ` Eli Zaretskii

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=200604121824.k3CIOuJm000173@elgar.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=drow@false.org \
    --cc=dtaylor@emc.com \
    --cc=gdb@sources.redhat.com \
    --cc=jr.peulve@wanadoo.fr \
    /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