Bug 1565775
Summary: | rebase elfutils in RHEL 7.6 | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | David Smith <dsmith> |
Component: | elfutils | Assignee: | Mark Wielaard <mjw> |
Status: | CLOSED ERRATA | QA Contact: | Martin Cermak <mcermak> |
Severity: | unspecified | Docs Contact: | Vladimír Slávik <vslavik> |
Priority: | unspecified | ||
Version: | 7.6 | CC: | bgollahe, mcermak, mjw, vslavik |
Target Milestone: | rc | Keywords: | Rebase |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | elfutils-0.172-1.el7 | Doc Type: | Rebase: Enhancements Only |
Doc Text: |
_elfutils_ rebased to version 0.172
The _elfutils_ packages have been upgraded to upstream version 0.172. This update adds support for the DWARF5 debug information format, split-dwarf, and GNU DebugFission:
* The `eu-readelf` tool can display split unit DIEs when the `--debug-dump=info+` option is used.
* The `eu-readelf` tool can inspect separate `.dwo` DWARF "skeleton files" with debug information when the `--dwarf-skeleton` option is used.
* The *libdw* library now tries to resolve the "alt file" containing linked debug information even when it has not yet been set with the `dwarf_set_alt()` function.
* The *libdw* library has been extended with the functions `dwarf_die_addr_die()`, `dwarf_get_units()`, `dwarf_getabbrevattr_data()` and `dwarf_cu_info()`.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2018-10-30 10:35:29 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1505884 |
Description
David Smith
2018-04-10 18:25:58 UTC
We are going with 0.172, which has not functional changes over 0.171, but lots of bug fixes for handling bad DWARF5 data. 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/RHEA-2018:3149 |