Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Several problems related to debuginfo were found in the glibc-2.12-1.25.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 symbolic links pointing to another path
-------------------------------------------------
Debuginfo package includes a symbolic link to each binary that has the debugging symbols stored there. For glibc, four symbolic links do not point to the right binary, and that makes it impossible to use build ids from a coredump to get a list of packages required by it. Usually, this is a packaging error caused usually by placing identical binary into several locations instead of creating a symlink. If one copy of the binary is SUID/SGID, it is not possible to use symlink. You can add a dependency on bug #727872 and rebuild glibc when that bug is fixed.
- affected binary: /usr/libexec/getconf/POSIX_V7_ILP32_OFFBIG
affected package: glibc-2.12-1.25.el6.i686
referenced binary: /usr/bin/getconf
referenced package: glibc-common-2.12-1.25.el6.i686
debuginfo symlink: /usr/lib/debug/.build-id/4e/99868ce716ef54e60cc64212dd6ba843b54d3b
- affected binary: /usr/libexec/getconf/POSIX_V6_ILP32_OFF32
affected package: glibc-2.12-1.25.el6.i686
referenced binary: /usr/bin/getconf
referenced package: glibc-common-2.12-1.25.el6.i686
debuginfo symlink: /usr/lib/debug/.build-id/4e/99868ce716ef54e60cc64212dd6ba843b54d3b
- affected binary: /usr/libexec/getconf/POSIX_V6_ILP32_OFFBIG
affected package: glibc-2.12-1.25.el6.i686
referenced binary: /usr/bin/getconf
referenced package: glibc-common-2.12-1.25.el6.i686
debuginfo symlink: /usr/lib/debug/.build-id/4e/99868ce716ef54e60cc64212dd6ba843b54d3b
- affected binary: /usr/libexec/getconf/POSIX_V7_ILP32_OFF32
affected package: glibc-2.12-1.25.el6.i686
referenced binary: /usr/bin/getconf
referenced package: glibc-common-2.12-1.25.el6.i686
debuginfo symlink: /usr/lib/debug/.build-id/4e/99868ce716ef54e60cc64212dd6ba843b54d3b
This issue has been solved in Fedora by /usr/lib/rpm/find-debuginfo.sh creating additional symlinks for identical binaries. However, symlinks should be used instead of duplicating a binary when possible.
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/libexec/pt_chown
affected package: glibc-common-2.12-1.25.el6.i686
binary contains debug sections (debuginfo script failed to find/strip it)
affected binary file mode: 104711
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.)
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.
http://rhn.redhat.com/errata/RHSA-2011-1526.html