Bug 754730 - GCC optimization hiding NULL-dereference bug
Summary: GCC optimization hiding NULL-dereference bug
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: gcc
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 754729
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-17 15:16 UTC by Stephen Gallagher
Modified: 2011-11-24 11:16 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 754729
Environment:
Last Closed: 2011-11-24 11:16:26 UTC
Type: ---


Attachments (Terms of Use)
Sample program demonstrating the issue (222 bytes, text/plain)
2011-11-17 15:17 UTC, Stephen Gallagher
no flags Details

Description Stephen Gallagher 2011-11-17 15:16:28 UTC
+++ This bug was initially created as a clone of Bug #754729 +++

Description of problem:
GCC optimization at level -O1 or higher hides a NULL-dereference bug in an 'if' statement.

Version-Release number of selected component (if applicable):
gcc-4.6.2-1.fc16.x86_64

How reproducible:
Every time.

Steps to Reproduce:
1. Compile the attached sample program with -O1, -O2 or -O3
  
Actual results:
Program runs to completion, returning success.

Expected results:
Program should crash due to a segmentation fault attempting to dereference 'ptr' in the IF statement.


Additional info:
If the attached program is built with -O0, the crash does not occur (and may hang around to cause unrelated issues later that are more difficult to track down).

Comment 1 Stephen Gallagher 2011-11-17 15:17:46 UTC
Created attachment 534209 [details]
Sample program demonstrating the issue

Comment 2 Jakub Jelinek 2011-11-24 11:16:26 UTC
That is fine, dereferencing a NULL pointer results in undefined behavior, when you reach such a statement the program can do anything, format your disk, segfault, anything else, and the compiler may optimize based on the assumption that it doesn't happen.


Note You need to log in before you can comment on or make changes to this bug.