Subject: Re: Enabling separate debug symbol support for gdb6
To: Luke Mewburn <lukem@NetBSD.org>
From: David Laight <firstname.lastname@example.org>
Date: 07/21/2006 19:21:52
On Tue, Jul 18, 2006 at 02:55:20AM +1000, Luke Mewburn wrote:
> Some questions:
> * Is this a good idea?
And for precisely the same reason that the decision was made to leave
the files unstripped in the first place.
Remember we don't compile stuff with -g, to the symbol table is just
the names of all the functions and data.
Although the symbol table remains in the disk file, it isn't in a part
of the file that gets loaded into memory. So splitting the information
into 2 files is just a complete waste of inodes and an extra relationship
that can easily get out of step.
Spliting out the main symbols will leave is in the state that M$ gets into,
where you don't have the .pdb files so can't even get a stack traceback
containing the names of global symbols.
You also want to read the discussions about the .eh_frame section in
amd64 binaries - the difficulty in removing it is partially based on
the fact that (excpet for kernels) it is almost never loaded into memory.
David Laight: email@example.com