Bug 16149 - tst-cleanup2 & tst-cleanupx2 failures since gcc r204414
Summary: tst-cleanup2 & tst-cleanupx2 failures since gcc r204414
Status: RESOLVED FIXED
Alias: None
Product: glibc
Classification: Unclassified
Component: nptl (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-10 13:03 UTC by Markus Trippelsdorf
Modified: 2014-06-13 12:19 UTC (History)
4 users (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:
fweimer: security-

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Trippelsdorf 2013-11-10 13:03:11 UTC 
Since gcc r204414 tst-cleanup2 & tst-cleanupx2 fail:

Attempting to sprintf to null ptr
Didn't expect signal from child: got `Illegal instruction'
Comment 1 law 2013-11-10 21:55:31 UTC 
GCC now has the ability to replace a NULL pointer dereference with a trap instruction.  This is useful in a variety of contexts as a path with a NULL pointer dereference is not standards conformant.

My recommendation would be to first test if -fno-isolate-erroneous-paths exists as an option and use it for that test.
Comment 2 Markus Trippelsdorf 2013-11-11 06:18:43 UTC 
I think you should leave the *0 in gcc, because you'll break
all programs that have a custom handler otherwise.

For example Xorg also breaks without -fno-isolate-erroneous-paths
on my machine:
...
[ 59279.226] (EE) Illegal instruction at address 0x452dc0
[ 59279.232] (EE) 
Fatal server error:
[ 59279.244] (EE) Caught signal 4 (Illegal instruction). Server aborting
Comment 3 Ondrej Bilka 2013-11-20 20:22:11 UTC 
Fixed by c8b82b81ded53ae06987727e807d19170bee4204.