Bug 1497800
| Summary: | something broken in ppc64 backtracing | ||
|---|---|---|---|
| Product: | DevTools | Reporter: | Martin Cermak <mcermak> |
| Component: | rust | Assignee: | Josh Stone <jistone> |
| Status: | CLOSED ERRATA | QA Contact: | Martin Cermak <mcermak> |
| Severity: | unspecified | Docs Contact: | Vladimír Slávik <vslavik> |
| Priority: | unspecified | ||
| Version: | rust-toolset-7 | CC: | emachado, jcajka, jistone, kanderso, law, sbharadw, tstellar, vslavik |
| Target Milestone: | rc | ||
| Target Release: | 2018.4 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause: Rust's backtrace library didn't support ppc64 ELFv1.
Consequence: Backtraces printed during Rust panics with RUST_BACKTRACE=1 showed "<unknown>" symbol information.
Fix: Rust's backtrace library has been updated in Rust 1.28 to include support for ppc64 ELFv1.
Result: RUST_BACKTRACE=1 shows appropriate symbols.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-11-13 15:24:31 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: | |||
|
Description
Martin Cermak
2017-10-02 17:22:20 UTC
Deferring to a future release, but we'll keep the bug open for tracking. Rust uses a fork of https://github.com/ianlancetaylor/libbacktrace, which is based on GCC's libbacktrace. It appears that code just didn't handle .opd at all, which you need for PPC64 ELFv1 (big-endian). This was reported in GCC 82368, fixed by Jakub in r257685, and will reach Rust in 1.28. Rather, GCC r257658 was the actual fix; r257685 was a followup tweak. 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:3584 |