A program compiled with -fstack-check option terminates abnormally with SIGSEGV. The issue occurs after update. We can see it by a simple reproducer, and it occurs about once every twice.
The issue does not occur without -fstack-check option, but the customer would like to use the option. Is there any other workaround with the option?
- Red Hat Enterprise Linux (RHEL) 6 and 7 on x86_64 architecture
- kernel-2.6.32-754.el6 and later
- kernel-2.6.32-696.10.1.el6 and later
- kernel-2.6.32-573.47.1.el6 and later
- kernel-2.6.32-504.63.2.el6 and later
- kernel-2.6.32-431.84.1.el6 and later
- kernel-2.6.32-358.82.1.el6 and later
- kernel-2.6.32-220.75.1.el6 and later
- gcc-4.4.6-3.el6.x86_64 used with
- kernel-3.10.0-693.el7 (from RHEL7.4GA) and later
- kernel-3.10.0-514.26.2.el7 (a RHEL7.3.z kernel) and later
- code compiled with
-fstack-check(either on RHEL6, or on RHEL7 with compat-gcc)
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.