RE: FW: Huge binaries

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> Sorry, Chris, I couldn't debug a stripped binary with gdb because the
computer said there wasn't any debugger information in that file.  
I'm hoping if I have a core from the stripped binary I can debug it with
the non-stripped version.

> Did the compiler tell your computer to optimize the programs that
caused the huge binaries?
Debug binaries are also larger:

1300MB - debug binary with 4.5.2
  59MB - debug build stripped
 850MB - debug build with 4.4.3
 180MB - release with 4.4.3
1200MB - release with 4.5.2
  45MB - strings of release with 4.5.2
  60MB - stripped release with 4.5.2

> By the way, years ago, when I used GNAT 95, Professor Michael Feldman
said that GNAT's linker would include in the binary each program from
every library the Ada 95 program needed.  If you told the machine to
optimize the binary, it only deleted the extra routines from the binary.

I'm not using ADA.  It's C++ with heave use of meta programming.  The
actual code the program needs to run isn't an issue.  It's the debug
information.


I did some playing with the different gcc flags for compiling a single
.o

218M -g2
 94M -g1 
 20M -g0
179M -femit-struct-debug-baseonly
218M -femit-struct-debug-reduced
218M -feliminate-dwarf2-dups
179M -femit-struct-debug-detailed=none
218M -fvar-tracking-assignments-toggle
218M -feliminate-unused-debug-types
173M -gstrict-dwarf
218M -ggdb
218M -feliminate-unused-debug-symbols
294M -gdwarf-version=4  (without -g)
216M -gdwarf-3 (without -g)

So it seems to be something in g2, but not in g1.  Is there anything
else I can turn off?


Chris


-----Original Message-----
From: Bill McEnaney [mailto:bill@xxxxxxxxxxxx] 
Sent: Tuesday, February 22, 2011 12:38 AM
To: Hite, Christopher; gcc-help@xxxxxxxxxxx
Subject: Re: FW: Huge binaries

Sorry, Chris, I couldn't debug a stripped binary with gdb because the
computer said there wasn't any debugger information in that file.  

Did the compiler tell your computer to optimize the programs that caused
the huge binaries?

By the way, years ago, when I used GNAT 95, Professor Michael Feldman
said that GNAT's linker would include in the binary each program from
every library the Ada 95 program needed.  If you told the machine to
optimize the binary, it only deleted the extra routines from the binary.

Cheers,
Bill
Chris Hite writes:

> Hi, I'm upgrading from 4.4.3  => 4.5.2 and the size of my already 
> large binaries got even bigger.
> 
> 60MB - stripped old or new
> 180MB - old release binary with debug info (-g) 1200MB - new compiler 
> with same flags
> 
> strings are only a small part of the debug info:
> 45MB - strings <binary>
> 
> I'm using a bunch of meta-programming.
> 
> Did something big happen between these versions?
> Are there any options between the stripped binary and the 1.2GB
version?
> Can I debug a core from a stripped binary using a non-stripped binary?
> 
> Chris
> 
> 

________________________________________________________________
Please visit a saintly hero:
http://www.jakemoore.org



[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux