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.
Improved DWARF 5 support in various tools
Support for the DWARF debugging format version 5 has been extended in the following tools:
* The `eu-readelf` tool from the _elfutils_ package now recognizes all DWARF 5 tags and attributes.
* The `readelf` and `objdump` tools from the _binutils_ package now recognize the DWARF 5 tag `DW_AT_exported_symbols` and correctly report its presence in debug information sections.
Created attachment 1301240[details]
clang compiled object that includes the example above
Description of problem:
We are starting to use Clang 4.0.0 at LLNL and it is emitting some DWARF5 opcodes. Please backport DWARF5 decoding to RHEL's binutils.
For example:
#include <string>
#include <vector>
std::vector<std::string> var;
and tangentially I saw something in the DWARF which neither readelf or eu-readelf understands.
<2><7e1>: Abbrev Number: 23 (DW_TAG_namespace)
<7e2> DW_AT_name : (indirect string, offset: 0x15c): __cxx11
<7e6> DW_AT_decl_file : 1
<7e7> DW_AT_decl_line : 2214
<7e9> Unknown AT value: 89: 1
probably a rebase is too dangerous and the changes haven't even landed in 2.28 yet. However, since clang is already emitting some DWARF5 we should at least be able to decode what it is emitting reliably.
Hi Ben,
Unfortunately this request has arrived too late to be included into RHEL 7.4.
I will make sure however that the RHEL 7.5 binutils does contain the required
patch.
In the meantime you might want to consider using the soon-to-be-released
Developer Toolset 7 for RHEL 7.4, as I have patched those sources as well.
Cheers
Nick
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://access.redhat.com/errata/RHBA-2018:0686
Created attachment 1301240 [details] clang compiled object that includes the example above Description of problem: We are starting to use Clang 4.0.0 at LLNL and it is emitting some DWARF5 opcodes. Please backport DWARF5 decoding to RHEL's binutils. For example: #include <string> #include <vector> std::vector<std::string> var; and tangentially I saw something in the DWARF which neither readelf or eu-readelf understands. <2><7e1>: Abbrev Number: 23 (DW_TAG_namespace) <7e2> DW_AT_name : (indirect string, offset: 0x15c): __cxx11 <7e6> DW_AT_decl_file : 1 <7e7> DW_AT_decl_line : 2214 <7e9> Unknown AT value: 89: 1 probably a rebase is too dangerous and the changes haven't even landed in 2.28 yet. However, since clang is already emitting some DWARF5 we should at least be able to decode what it is emitting reliably.