[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: unstripped files



-----BEGIN PGP SIGNED MESSAGE-----

Michael Meskes, in an immanent manifestation of deity, wrote:
>./usr/lib/perl5/i386-linux/5.004/auto/DBI/DBI.so
>./usr/lib/perl5/i386-linux/5.004/auto/MD5/MD5.so
>./usr/lib/perl5/i386-linux/5.004/auto/MIME/Base64/Base64.so
>./usr/lib/perl5/i386-linux/5.004/auto/Tk/Menubutton/Menubutton.so
>./usr/lib/perl5/i386-linux/5.004/auto/Tk/Bitmap/Bitmap.so
>./usr/lib/perl5/i386-linux/5.004/auto/Tk/Canvas/Canvas.so
>./usr/lib/perl5/i386-linux/5.004/auto/Tk/Entry/Entry.so
>./usr/lib/perl5/i386-linux/5.004/auto/Tk/HList/HList.so
>./usr/lib/perl5/i386-linux/5.004/auto/Tk/IO/IO.so
>./usr/lib/perl5/i386-linux/5.004/auto/Tk/InputO/InputO.so
>./usr/lib/perl5/i386-linux/5.004/auto/Tk/Listbox/Listbox.so
>./usr/lib/perl5/i386-linux/5.004/auto/Tk/NBFrame/NBFrame.so
>./usr/lib/perl5/i386-linux/5.004/auto/Tk/Mwm/Mwm.so
>./usr/lib/perl5/i386-linux/5.004/auto/Tk/Scrollbar/Scrollbar.so
>./usr/lib/perl5/i386-linux/5.004/auto/Tk/Photo/Photo.so
>./usr/lib/perl5/i386-linux/5.004/auto/Tk/Pixmap/Pixmap.so
>./usr/lib/perl5/i386-linux/5.004/auto/Tk/Scale/Scale.so
>./usr/lib/perl5/i386-linux/5.004/auto/Tk/Text/Text.so
>./usr/lib/perl5/i386-linux/5.004/auto/Tk/Xlib/Xlib.so
>./usr/lib/perl5/i386-linux/5.004/auto/Tk/X/X.so
>./usr/lib/perl5/i386-linux/5.004/auto/Tk/Tk.so
>./usr/lib/perl5/i386-linux/5.004/auto/Tk/TixGrid/TixGrid.so
>./usr/lib/perl5/i386-linux/5.004/auto/Tk/TList/TList.so
>./usr/lib/perl5/i386-linux/5.004/auto/Data/Dumper/Dumper.so
>
>Are these shared libraries? If so the can/should be stripped as the symbols
>are not used anyway. Shared libraries have another symbol table.

These can most likely be stripped.  In my Perl debian/rules, I have:
find debian -name '*.so' -print0 | xargs --null strip --strip-unneeded

This is probably something that should be done for all Perl loadable
modules unless there's something that breaks when we do.

>./usr/bin/dperl5.00404
>./usr/bin/debugperl
>
>Are the symbols need here?

Yes, this is specifically the point of debugperl.  Note the following
from the extended description of debugperl that it is used to debug Perl 
itself and therefore needs the debugging symbols:
 debugperl will allow you to see the internal data for Perl.  It will
 allow you to view the compiled opcode tree, see *exactly* how a regex
 is being used, and show (in minute detail) what Perl is doing.  Look in 
 perlrun(1p) for details.
 .
 You probably don't need this.  perl -dead will bring up the Perl source 
 debugger and tell you much of what you want to know.  See perldebug(1).

Darren
- -- 
<torin@daft.com> <http://www.daft.com/~torin> <torin@debian.org> <torin@io.com>
Darren Stalder/2608 Second Ave, @282/Seattle, WA 98121-1212/USA/+1-800-921-4996
@ Sysadmin, webweaver, postmaster for hire. C/Perl/CGI/Pilot programmer/tutor @
@		     Make a little hot-tub in your soul.		      @

-----BEGIN PGP SIGNATURE-----
Version: 2.6.3a
Charset: noconv
Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface

iQCVAwUBNlEGKI4wrq++1Ls5AQGJsgP+KaGR5oBgla8rdBQkg+UpdzIoi/d+8Wrv
HE4N/tuBX4Bl5xef/Al/2sF6y5Mifrg+7hJSYJzgQsXo1HTdd7IjIdk/kS1+rYf6
vQcz16+0fx+NdyJM6hN7K+iGkuLHWnX/BCanwdoNmx6RY0cPst6+wTRIaBQE/tzC
ewv4W/J45J4=
=iLZi
-----END PGP SIGNATURE-----


Reply to: