This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Huge Increase in Unstripped Executable Size G++ 2.95 to 3.2
- From: Daniel Jacobowitz <drow at mvista dot com>
- To: "Michael S. Zick" <mszick at goquest dot com>
- Cc: Jim Wilson <wilson at tuliptree dot org>, Andi Kleen <ak at suse dot de>,gcc at gcc dot gnu dot org
- Date: Sat, 1 Mar 2003 11:12:08 -0500
- Subject: Re: Huge Increase in Unstripped Executable Size G++ 2.95 to 3.2
- References: <20030227.154544.18888.253032@webmail06.lax.untd.com.suse.lists.egcs> <03030107230500.01209@wolf466>
On Sat, Mar 01, 2003 at 07:23:05AM -0600, Michael S. Zick wrote:
> On Wednesday 31 December 1969 05:59 pm, Jim Wilson wrote:
> >
> > Shared libraries are a different matter. The debug info would have to
> > be in the shared library, or you would have to keep the original
> > objects. Either way there doesn't seem to be much benefit here for
> > shared libraries.
> >
> > Jim
> Noticed recently on the BinUtils list was a patch to put the debug
> info into a seperate (debug info only) object file.
>
> That patch was to support the VxWorks tools but it might be the
> answer here.
> The executable object has non-debug code only (small) and
> the debug info is still available in the associated
> debug object file.
>
> I don't follow the gdb list - I don't know if gdb can handle the
> "two file" format.
GDB supports something similar, although I think it's different from
the patch you're talking about. Search for .gnu_debuglink.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer