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.
Cause: When provided a binary that was located in the same current working directory (CWD), gdb-add-index script was not correctly handling the path to it.
Consequence: The user could not specify a binary without using its full or relative path (e.g., "gdb-add-index a.out" would not work).
Fix: gdb-add-index was modified in order to correctly handle all kinds of paths.
Result: The user can now specify a binary without needing to specify its full or relative path in the filesystem.
The first thing I tried:
# gdb-add-index a.out
Error while writing index for `/root/a.out': Can't open `a.out/a.out.gdb-index' for writing
Maybe it's a small thing, but I would replace
dir="${file%/*}"
with
[[ $file == */* ]] && dir="${file%/*}" || dir="."
...or perhaps even use dirname, even though it's an external command.
Comment 1Sergio Durigan Junior
2014-09-04 18:50:31 UTC
I prefer the dirname approach. I am preparing a patch.
Comment 2Sergio Durigan Junior
2014-09-04 18:56:45 UTC
Thinking more about the issue, the upstream version of the script does:
test "$dir" = "$file" && dir="."
So, in order to keep compatibility with upstream, I will use this construction as well.
Comment 3Sergio Durigan Junior
2014-09-30 21:07:48 UTC
Fix pushed to RHEL-7.1 branch.
QE: I have not added a specific GDB testcase because it is much easier for QE to test it using your own testing infrastructure.
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-2015-0404.html
The first thing I tried: # gdb-add-index a.out Error while writing index for `/root/a.out': Can't open `a.out/a.out.gdb-index' for writing Maybe it's a small thing, but I would replace dir="${file%/*}" with [[ $file == */* ]] && dir="${file%/*}" || dir="." ...or perhaps even use dirname, even though it's an external command.