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 java-1.6.0-openjdk-1.6.0.0-1.39.1.9.8.el6_1 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 package includes a symbolic link to each binary that has the debugging symbols stored there. For java-1.6.0-openjdk, 11 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 java-1.6.0-openjdk when that bug is fixed.
- affected binary: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre/bin/java
affected package: java-1.6.0-openjdk-1.6.0.0-1.39.1.9.8.el6_1.i686
referenced binary: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/bin/java
referenced package: java-1.6.0-openjdk-devel-1.6.0.0-1.39.1.9.8.el6_1.i686
debuginfo symlink: /usr/lib/debug/.build-id/1e/8339e2439739e2df3262cfc6282b19dc57f15a
- affected binary: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre/bin/rmid
affected package: java-1.6.0-openjdk-1.6.0.0-1.39.1.9.8.el6_1.i686
referenced binary: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/bin/rmid
referenced package: java-1.6.0-openjdk-devel-1.6.0.0-1.39.1.9.8.el6_1.i686
debuginfo symlink: /usr/lib/debug/.build-id/14/853253be400604bf9bebb821c9a2142dbe4db0
- affected binary: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre/bin/unpack200
affected package: java-1.6.0-openjdk-1.6.0.0-1.39.1.9.8.el6_1.i686
referenced binary: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/bin/unpack200
referenced package: java-1.6.0-openjdk-devel-1.6.0.0-1.39.1.9.8.el6_1.i686
debuginfo symlink: /usr/lib/debug/.build-id/84/527fa4c72b31b4568c79f0bd0ed2fe81e8f497
- affected binary: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre/bin/pack200
affected package: java-1.6.0-openjdk-1.6.0.0-1.39.1.9.8.el6_1.i686
referenced binary: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/bin/pack200
referenced package: java-1.6.0-openjdk-devel-1.6.0.0-1.39.1.9.8.el6_1.i686
debuginfo symlink: /usr/lib/debug/.build-id/dc/54903d661b96740ad94d5d7e964ddba82a1393
- affected binary: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre/bin/rmiregistry
affected package: java-1.6.0-openjdk-1.6.0.0-1.39.1.9.8.el6_1.i686
referenced binary: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/bin/rmiregistry
referenced package: java-1.6.0-openjdk-devel-1.6.0.0-1.39.1.9.8.el6_1.i686
debuginfo symlink: /usr/lib/debug/.build-id/1c/8f96730d8f279037a6f175317786c3e79e4d0c
- affected binary: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre/bin/orbd
affected package: java-1.6.0-openjdk-1.6.0.0-1.39.1.9.8.el6_1.i686
referenced binary: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/bin/orbd
referenced package: java-1.6.0-openjdk-devel-1.6.0.0-1.39.1.9.8.el6_1.i686
debuginfo symlink: /usr/lib/debug/.build-id/10/52c94ac2b516487146e4c168bdc62556937fb4
- affected binary: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre/bin/policytool
affected package: java-1.6.0-openjdk-1.6.0.0-1.39.1.9.8.el6_1.i686
referenced binary: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/bin/policytool
referenced package: java-1.6.0-openjdk-devel-1.6.0.0-1.39.1.9.8.el6_1.i686
debuginfo symlink: /usr/lib/debug/.build-id/a0/aada5d6771246a7963789a465dfd673a8b30a0
- affected binary: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre/bin/tnameserv
affected package: java-1.6.0-openjdk-1.6.0.0-1.39.1.9.8.el6_1.i686
referenced binary: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/bin/tnameserv
referenced package: java-1.6.0-openjdk-devel-1.6.0.0-1.39.1.9.8.el6_1.i686
debuginfo symlink: /usr/lib/debug/.build-id/73/a99abaae57abf6204d05c8df6db3de2793c7a3
- affected binary: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre/bin/keytool
affected package: java-1.6.0-openjdk-1.6.0.0-1.39.1.9.8.el6_1.i686
referenced binary: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/bin/keytool
referenced package: java-1.6.0-openjdk-devel-1.6.0.0-1.39.1.9.8.el6_1.i686
debuginfo symlink: /usr/lib/debug/.build-id/48/c577a2f1b94e9cb112c89fdc2fe695414ab72a
- affected binary: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre/bin/servertool
affected package: java-1.6.0-openjdk-1.6.0.0-1.39.1.9.8.el6_1.i686
referenced binary: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/bin/servertool
referenced package: java-1.6.0-openjdk-devel-1.6.0.0-1.39.1.9.8.el6_1.i686
debuginfo symlink: /usr/lib/debug/.build-id/68/5a294dac7609674125e05da5d9d4ed12e12385
- affected binary: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre/lib/jexec
affected package: java-1.6.0-openjdk-1.6.0.0-1.39.1.9.8.el6_1.i686
referenced binary: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/lib/jexec
referenced package: java-1.6.0-openjdk-devel-1.6.0.0-1.39.1.9.8.el6_1.i686
debuginfo symlink: /usr/lib/debug/.build-id/8b/52e1794d7abb9336dbf2931d6e12723450ef29
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.
(This bug was detected and filed by a script.)
Thanks for the pointer to 727872. I will add a dependency on it.
We do not use any setuid/setguid. The duplicated binaries are a result of upstream JDK build and I think it would be best left untouched unless unavoidable.
Comment 3RHEL Program Management
2011-10-07 14:54:05 UTC
Since RHEL 6.2 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.
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.
Adding Pavel from QE on our side to cc:
Pavel, please see above bug. I don't think this is really an issue and do not want to add symlinks as it changes what upstream distributes and apps might rely on there being binaries rather than symlinks in some places.
Are you okay with closing this issue?