Debug symbols for python module shared libraries (dbgsym packages) are not found by gdb

Bug #552432 reported by mikbini
30
This bug affects 6 people
Affects Status Importance Assigned to Milestone
python-support (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: python-central

If I use gdb on a python process that uses module shared libraries I get the following:

$ echo q |gdb /usr/bin/python 1863 |grep 'OpenSSL'
Reading symbols from /usr/lib/pymodules/python2.6/OpenSSL/rand.so...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/pymodules/python2.6/OpenSSL/rand.so
Reading symbols from /usr/lib/pymodules/python2.6/OpenSSL/crypto.so...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/pymodules/python2.6/OpenSSL/crypto.so
Reading symbols from /usr/lib/pymodules/python2.6/OpenSSL/SSL.so...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/pymodules/python2.6/OpenSSL/SSL.so

But:

$ dpkg -l python-openssl python-openssl-dbgsym
[...]
ii python-openssl 0.10-1 Python wrapper around the OpenSSL library
ii python-openssl-dbgsym 0.10-1 debug symbols for package python-openssl

And

$ dpkg -L python-openssl-dbgsym
/.
/usr
/usr/lib
/usr/lib/debug
/usr/lib/debug/usr
/usr/lib/debug/usr/lib
/usr/lib/debug/usr/lib/python2.6
/usr/lib/debug/usr/lib/python2.6/dist-packages
/usr/lib/debug/usr/lib/python2.6/dist-packages/OpenSSL
/usr/lib/debug/usr/lib/python2.6/dist-packages/OpenSSL/crypto.so
/usr/lib/debug/usr/lib/python2.6/dist-packages/OpenSSL/rand.so
/usr/lib/debug/usr/lib/python2.6/dist-packages/OpenSSL/SSL.so

So the symbol files are there but gdb cannot find them. OpenSSL is only an example, this actually happens with any python -dbgsym package.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: python-central 0.6.11ubuntu13
ProcVersionSignature: Ubuntu 2.6.32-18.27-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-18-generic i686
NonfreeKernelModules: wl
Architecture: i386
Date: Wed Mar 31 10:41:06 2010
InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info'
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: python-central

Revision history for this message
mikbini (mikbini) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in python-central (Ubuntu):
status: New → Confirmed
todaioan (alan-ar06)
Changed in python-central (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Edward Donovan (edward.donovan) wrote :

I don't know any reason to think this bug has been fixed. I think 'toda' has been making some changes that they may not understand. Anyone who has privileges to change it back, would be welcome. Thanks.

Matthias Klose (doko)
affects: python-central (Ubuntu) → python-support (Ubuntu)
Changed in python-support (Ubuntu):
status: Fix Released → Triaged
Revision history for this message
Edward Donovan (edward.donovan) wrote :

Thanks so much, Matthias.

Revision history for this message
Oliver Gerlich (ogerlich) wrote :

Same problem here on 12.04, for libavformat53-dbgsym 4:0.8.5-0ubuntu0.12.04.1 . I don't quite understand how gdb looks up the debug library; but at least the .gnu_debuglink section in the installed lib is weird:

$ objdump -s -j .gnu_debuglink /usr/lib/i386-linux-gnu/i686/cmov/libavformat.so.53

/usr/lib/i386-linux-gnu/i686/cmov/libavformat.so.53: file format elf32-i386

Contents of section .gnu_debuglink:
 0000 34313238 63353066 61386161 35363030 4128c50fa8aa5600
 0010 61306332 36383061 61653835 39313465 a0c2680aae85914e
 0020 31336665 63342e64 65627567 00000000 13fec4.debug....
 0030 3638cf88 68..

The section should contain the name of the debug lib, and its hash. In this case it specifies 4128c50fa8aa5600a0c2680aae85914e13fec4.debug as name (rather than libavformat.so.53.21.1 , which is the only file name installed by libavformat53-dbgsym).

Maybe this is the same problem as described in bug 1040645 which is reported and fixed for 12.10.

Revision history for this message
dino99 (9d9) wrote :

Support for that version has ended

Changed in python-support (Ubuntu):
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.