Bug 1443236
Summary: | Applications encounter SIGSEGV when LD_LIBRARY_PATH LD_LIBRARY_PATH contains only non-existings paths | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Kyle Walker <kwalker> |
Component: | glibc | Assignee: | DJ Delorie <dj> |
Status: | CLOSED ERRATA | QA Contact: | Sergey Kolosov <skolosov> |
Severity: | medium | Docs Contact: | Vladimír Slávik <vslavik> |
Priority: | medium | ||
Version: | 7.3 | CC: | ashankar, codonell, cww, dj, fweimer, jwright, mcermak, mnewsome, pfrankli, skolosov, troels, vslavik |
Target Milestone: | rc | Keywords: | Patch |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | glibc-2.17-197.el7 | Doc Type: | Bug Fix |
Doc Text: |
Segmentation faults in applications because of only non-existent paths in *LD_LIBRARY_PATH* no longer happen
Previously, when the *LD_LIBRARY_PATH* environment variable contained only non-existent paths, the dynamic loader produced a segmentation fault. Consequently, applications terminated unexpectedly with a segmentation fault at startup in the described situation. The dynamic loader has been fixed. As a result, applications no longer terminate unexpectedly in the described situation.
Note that updating the _glibc_ package is enough to fix this bug for any affected applications.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2018-04-10 13:58:28 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: | |
Bug Depends On: | 1184234 | ||
Bug Blocks: | 1420851, 1471969 |
Description
Kyle Walker
2017-04-18 20:15:16 UTC
Thanks for reporting this. We will be looking at this bug as part of our review for RHEL 7.5. If you need a fix sooner please add more information to this bug report. The immediate workaround is to set LD_LIBRARY_PATH in such a way as to avoid the issue. 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/RHSA-2018:0805 |