Re: Binaries with debug symbols

Am Sonntag, 4. April 2004 13:36 schrieb Pablo Pita Leira:
> El Saturday 03 April 2004 15:47, Mat=EDas Costa escribi=F3:
> > And then I think, why not compiling the packages with debug symbols? The
> > only reason I found is theses binaries should be bigger and slower. But
> > we have to see these packages are not for the normal user. May be we can
> > call the users of these packages a power-user (may be no, I am not one)
> > or bledding-edge user, or kde-compromised user. I want to callaborate
> > with the KDE
> > development, and my (our) 2 cents can be good bug reports.
>
> I personally prefer not getting packages with debug symbols, and I like t=
he
> fact that we get packages optimized for i686. I do not use a fast machine,
> and I appreciate having KDE CVS workable. Besides, you do not always need=
 a
> backtrace to report bugs. Quite often, just providing in the bug report an
> easy way for the developers to reproduce it is the way to go.

Debug packages are not that much slower than without debug.

>
> > If someone does not want the inconveniences of the debug symbols he can
> > simply:
> >
> > dpkg -L package-name | grep ^/usr/bin | xargs strip
>
> This is not enough, because you will find symbols in the libraries.
> # dpkg -L kopete | fgrep \.so | wc -l
> 38
>
> Do not do a plain strip on the libraries. Plain strip would discard all
> symbols and that would affect loading the library. I suppose it would be
> safe to do strip --debug-only.

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 associa=
ted
           "-dbg" package. dh_strip will, when stripping off the debug symb=
ols
           of files in the given package, save them to independent files in
           the package build directory for the "-dbg" package.
           [...]

cu

=46abian