Why are the python binary and associated libraries stripped?

Asked by Bob Van Zant on 2013-06-27

I think this one is fairly simple. The python binary and libraries are all stripped. Is there a good reason why this is done? It makes debugging core files from python ~impossible.

The python-dbg package is compiled with a very different set of functionality and thus its symbols cannot be used to debug a core file in non-debug python.

At the least I'd love it if for the 14.x series of Ubuntu we could consider leaving symbols on these binaries.

$ file /usr/bin/python2.7
/usr/bin/python2.7: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.24, BuildID[sha1]=0x2aa581a3fdfce6d695bccad220e7f2a19db9abfa, stripped

$ file /usr/lib/libpython2.7.so.1.0
/usr/lib/libpython2.7.so.1.0: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=0x8c050160362a346af67b9cb31ef6b84d45223b69, stripped

Question information

English Edit question
Ubuntu python-defaults Edit question
No assignee Edit question
Last query:
Last reply:
N1ck 7h0m4d4k15 (nicktux) said : #1

Better for you (to take an answer) would be to open a bug-like question about python.
You can report a bug against python in Ubuntu and developers will answer to you.

How to report a bug


Can you help with this problem?

Provide an answer of your own, or ask Bob Van Zant for more information if necessary.

To post a message you must log in.