Bug 1488889
Summary: | s390x: binutils strip tool segfaults | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | David Hildenbrand <dhildenb> |
Component: | binutils | Assignee: | Nick Clifton <nickc> |
Status: | CLOSED ERRATA | QA Contact: | Miloš Prchlík <mprchlik> |
Severity: | unspecified | Docs Contact: | Vladimír Slávik <vslavik> |
Priority: | unspecified | ||
Version: | 7.5 | CC: | dhildenb, fweimer, law, mcermak, mprchlik, ohudlick, thuth, vslavik |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | s390x | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | binutils-2.27-16.base.el7 | Doc Type: | Bug Fix |
Doc Text: |
The *strip* utility works again
Previously, the BFD library missed a NULL pointer check on the IBM z Systems architecture. As a consequence, running the *strip* utility caused a segmentation fault. This bug has been fixed, and *strip* now works as expected.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2018-04-10 09:59:05 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
David Hildenbrand
2017-09-06 12:01:40 UTC
(new try after I pushed the enter key too early ...) Description of problem: While playing with the patch for bz 1485398, I noticed that the strip command is completely broken on s390x. Version-Release number of selected component (if applicable): binutils-2.27-15.base.el7 How reproducible: 100% Steps to Reproduce: 1. Create a simple C program test.c: int main() { return 0; } 2. Compile it $ gcc test.c -o test 3. Try to strip it using the strip tool $ strip --strip-unneeded test -o test.strip Actual results: "Segmentation fault" Expected results: No segmentation fault. Fixed in binutils-2.27-16.base.el7 Verified with binutils-2.27-27.base.el7.s390x. 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 |