Bug 729038 - Invalid symbolic link in debuginfo package
Summary: Invalid symbolic link in debuginfo package
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: gnuplot
Version: 6.3
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Pavel Cahyna
QA Contact: BaseOS QE - Apps
Depends On: 727872 836966
Blocks: 727919
TreeView+ depends on / blocked
Reported: 2011-08-08 15:20 UTC by Karel Klíč
Modified: 2017-12-06 11:01 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2017-12-06 11:01:40 UTC

Attachments (Terms of Use)

Description Karel Klíč 2011-08-08 15:20:38 UTC
A problem related to debuginfo was found in the gnuplot-4.2.6-2.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 package includes a symbolic link to each binary that has the debugging symbols stored there. For gnuplot, 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 gnuplot when that bug is fixed.

affected binary: /usr/bin/gnuplot-minimal
affected package: gnuplot-minimal-4.2.6-2.el6.i686
referenced binary: /usr/bin/gnuplot-wx
referenced package: gnuplot-4.2.6-2.el6.i686
debuginfo symlink: /usr/lib/debug/.build-id/b7/59f70c6c7cdfb867359194eeb0100d62942173

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.)

Comment 2 RHEL Product and Program Management 2011-08-08 15:41:23 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

Comment 4 Jan Kurik 2017-12-06 11:01:40 UTC
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:


Note You need to log in before you can comment on or make changes to this bug.