Several problems related to debuginfo were found in the sip-4.9.3-1.el6 package. These issues might affect crash analysis done by Automatic Bug Reporting Tool and its retrace server, and also prevent proper debugging of crashes via GDB.
Debuginfo missing for binaries
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/lib/python2.6/site-packages/sip.so
affected package: sip-4.9.3-1.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.
Source file missing in debuginfo package
A source file that was used by the compiler to generate a binary is missing from the debuginfo package. This is usually caused by the build script creating temporary source files during the build and deleting them after usage, or by moving source files between directories. Missing source files in debuginfo packages make debugging of crashes more difficult.
debuginfo package: sip-debuginfo-4.9.3-1.el6.i686
debuginfo file: /usr/lib/debug/usr/bin/sip.debug
missing source: /usr/src/debug/sip-4.9.3/sipgen/lexer.c.tmp
Please consider changing the package build script (if that is the cause of this issue) to keep the source files on their compilation place, so rpmbuild can find them when generating debuginfo package.
(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
it looks like the buildscript script creating temporary source files during the build and deleting them after usage,
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.
The official life cycle policy can be reviewed here:
This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL: