Re: Binaries with debug symbols

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 t=
he
> KDE
> development, and my (our) 2 cents can be good bug reports.

I personally prefer not getting packages with debug symbols, and I like the=
=20
fact that we get packages optimized for i686. I do not use a fast machine,=
=20
and I appreciate having KDE CVS workable. Besides, you do not always need a=
=20
backtrace to report bugs. Quite often, just providing in the bug report an=
=20
easy way for the developers to reproduce it is the way to go.=20

>
> 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.=20
# dpkg -L kopete | fgrep \.so | wc -l
38

Do not do a plain strip on the libraries. Plain strip would discard all=20
symbols and that would affect loading the library. I suppose it would be sa=
fe=20
to do strip --debug-only.

Pablo Pita=20