Re: Binaries with debug symbols

El Sunday 04 April 2004 18:31, Fabian Franz escribi=F3:
>
> Debug packages are not that much slower than without debug.
Valid point. But the symbols take place in memory.  We  know  that executab=
les=20
with debug information are much bigger, so you increase the strain on the=20
system. I am writting my response on KMail on a Celeron 433 MHz with 192 MB=
=20
of RAM and KDE is usable, but I see that I get swaping if I have a few=20
applications open (a desktop with some candy and applets in kicker, a few=20
tabs in konqueror, kmail).=20

>
> Afaik debians build process even includes a dh_strip ...
>
> Heh, and it even has a solution for this problem (from the man page):
>
>  --dbg-package=3Dpackage
>            This option tells dh_strip that the given package has an
> associated "-dbg" package. dh_strip will, when stripping off the debug
> symbols of files in the given package, save them to independent files in
> the package build directory for the "-dbg" package.
>            [...]

Nice to know about dh_strip.  I had to read the man page. It seems that wit=
h=20
it, the debian packager can compile, for example, kdelibs with debug symbol=
s,=20
then apply dh_strip --dbg-packge=3Dkdelibs in the build directory, and the=
=20
libraries would be stripped off their symbols. From there, the libraries in=
=20
the kdelibs deb would we stripped (good for me), and interested developers=
=20
would get a kdelibs-dbg deb package with the debugging symbols. It is=20
interesting.=20

If this would work, how would affect installing ? That is, we would do =20
apt-get install kdelibs and if we wanted to add debugging symbols, we would=
=20
also do  apt-get install kdelibs-dbg, is that correct ?

Pablo Pita=20