Red Hat Bugzilla – Bug 729009
Debug file missing in debuginfo package for a binary
Last modified: 2013-03-03 18:03:05 EST
A problem related to debuginfo was found in the libtar-1.2.11-16.el6 package. This issue might affect crash analysis done by Automatic Bug Reporting Tool and its retrace server, and also prevent proper debugging of crashes via GDB.
A debuginfo file for a binary is not present in the debuginfo package. This might be caused by:
- binary being compiled without debugging information
- debugging information being removed from the binary by a build script
- rpmbuild failing to extract debugging information from a binary in a buildroot because of permissions (eg. suid binaries, binaries without executable flag set)
affected binary: /usr/bin/libtar
affected package: libtar-1.2.11-16.el6.i686
binary doesn't contain debug sections (it was probably stripped)
affected binary file mode: 100755
This issue can be investigated by using eu-readelf tool from the elfutils package. Use `eu-readelf --notes /path/to/binary` to get build ID of a binary. Then check that the debuginfo package does not contain /usr/lib/debug/.build-id/<aa>/<bbbbbbbb>, where <aa> are the first two chars of the build ID, and <bbbbbbbb> is the rest of it. It should be a symlink pointing back to the binary.
(This bug was detected and filed by a script.)
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
fixed in libtar-1.2.11-21.fc17:
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.