Re: Bug#396365: please add a gdb .udeb, for easier debugging inside d-i

[Sven Luther <sven.luther@wanadoo.fr>]

On Tue, Oct 31, 2006 at 05:09:46PM +0200, Eddy Petrișor wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Sven Luther wrote:
> > My impression is that d-i loads the full libraries later on, or something
> > such.
> 
> AFAIK, this never happens. The reduction is done mainly for the thing
> not to be too big in the memory while running.

Hi Eddy,

I wonder how the current situation works for .udebs not in the image ? How do
you find out whose symbols are used by them and know not to strip them ? Is
this just luck ? I sincerely doubt that.

> > In any case if you have a better idea on how to do this, maybe having a
> > statically built gdb, it would be welcome too.
> 
> A statically built gdb is he way to go, IMHO.
> 
> If you'd want a udeb for gdb, then the library reduction should take
> into account its dependencies (symbols). This would mean:
> - - either you make a custom image which uses mklibs-copy (no reduction)
> and you can use a regular binary or a gdb udeb which contains just the
> gdb binary (dynamically linked)
> - - build a custom image with gdb's needed symbols not stripped - but this
> means that gdb could not be used for regulaly built images.

We need a custom image anyway, since we need a -debug version of the
binaries we want to debug.

Friendly,

Sven Luther