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.
A problem related to debuginfo was found in the db4-4.7.25-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.
Debuginfo files for some binaries are 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)
List of binaries without corresponding debuginfo file:
- affected binary: /usr/bin/db_load
affected package: db4-utils-4.7.25-16.el6.i686
binary doesn't contain debug sections (it was probably stripped)
affected binary file mode: 100755
- affected binary: /usr/bin/db_printlog
affected package: db4-utils-4.7.25-16.el6.i686
binary doesn't contain debug sections (it was probably stripped)
affected binary file mode: 100755
- affected binary: /usr/bin/db_dump185
affected package: db4-utils-4.7.25-16.el6.i686
binary doesn't contain debug sections (it was probably stripped)
affected binary file mode: 100755
- affected binary: /usr/bin/db_archive
affected package: db4-utils-4.7.25-16.el6.i686
binary doesn't contain debug sections (it was probably stripped)
affected binary file mode: 100755
- affected binary: /usr/bin/db_recover
affected package: db4-utils-4.7.25-16.el6.i686
binary doesn't contain debug sections (it was probably stripped)
affected binary file mode: 100755
- affected binary: /usr/bin/db_hotbackup
affected package: db4-utils-4.7.25-16.el6.i686
binary doesn't contain debug sections (it was probably stripped)
affected binary file mode: 100755
- affected binary: /usr/bin/berkeley_db_svc
affected package: db4-utils-4.7.25-16.el6.i686
binary doesn't contain debug sections (it was probably stripped)
affected binary file mode: 100755
- affected binary: /usr/bin/db_upgrade
affected package: db4-utils-4.7.25-16.el6.i686
binary doesn't contain debug sections (it was probably stripped)
affected binary file mode: 100755
- affected binary: /usr/bin/db_codegen
affected package: db4-utils-4.7.25-16.el6.i686
binary doesn't contain debug sections (it was probably stripped)
affected binary file mode: 100755
- affected binary: /usr/bin/db_stat
affected package: db4-utils-4.7.25-16.el6.i686
binary doesn't contain debug sections (it was probably stripped)
affected binary file mode: 100755
- affected binary: /usr/bin/db_verify
affected package: db4-utils-4.7.25-16.el6.i686
binary doesn't contain debug sections (it was probably stripped)
affected binary file mode: 100755
- affected binary: /usr/bin/db_checkpoint
affected package: db4-utils-4.7.25-16.el6.i686
binary doesn't contain debug sections (it was probably stripped)
affected binary file mode: 100755
- affected binary: /usr/bin/db_deadlock
affected package: db4-utils-4.7.25-16.el6.i686
binary doesn't contain debug sections (it was probably stripped)
affected binary file mode: 100755
- affected binary: /usr/bin/db_dump
affected package: db4-utils-4.7.25-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.)
Comment 2RHEL Program Management
2011-08-08 15:42:21 UTC
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
representative.
Oracle Makefile was stripping debuginfo from binaries during `make install`. Fixed by disabling the strip (by passing /bin/true as the strip command).
Comment 6RHEL Program Management
2013-10-14 01:01:45 UTC
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 unable to address this
request at this time.
Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.
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.
https://rhn.redhat.com/errata/RHBA-2017-0609.html