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 postgresql-8.4.7-2.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 link pointing to another path
------------------------------------------------
Debuginfo package includes a symbolic link to each binary that has the debugging symbols stored there. For postgresql, one symbolic link does 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 postgresql when that bug is fixed.
affected binary: /usr/lib/pgsql/test/regress/pg_regress
affected package: postgresql-test-8.4.7-2.el6.i686
referenced binary: /usr/lib/pgsql/pgxs/src/test/regress/pg_regress
referenced package: postgresql-devel-8.4.7-2.el6.i686
debuginfo symlink: /usr/lib/debug/.build-id/d3/e0e641035e9c7cfd8dafeaed34f677eaf607a6
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
------------------------------
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/lib/pgsql/test/regress/autoinc.so
affected package: postgresql-test-8.4.7-2.el6.i686
binary doesn't contain debug sections (it was probably stripped)
affected binary file mode: 100755
- affected binary: /usr/lib/pgsql/test/regress/regress.so
affected package: postgresql-test-8.4.7-2.el6.i686
binary doesn't contain debug sections (it was probably stripped)
affected binary file mode: 100755
- affected binary: /usr/lib/pgsql/test/regress/refint.so
affected package: postgresql-test-8.4.7-2.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:41:12 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.
Created attachment 531145[details]
patch for spec file
This patch removes unnecessary strip call and creates a symlink of pg_regress from -test to -devel subpackage to have the binary in only one package.
Per comment #1, this should be already resolved for RHEL6 (see the depends on
bug) -- and Honza fixed this properly for Fedora (soon enough to have it
inherited in RHEL7). This looks like a leftover bug and thus I'm closing..