Bug 506969 - (rpalermo_gcc_1) gcc: Internal error: Segmentation fault (program cc1)
gcc: Internal error: Segmentation fault (program cc1)
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: gcc (Show other bugs)
All Linux
low Severity high
: rc
: ---
Assigned To: Jakub Jelinek
Depends On:
  Show dependency treegraph
Reported: 2009-06-19 11:36 EDT by rpalermo
Modified: 2012-06-20 09:29 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-06-20 09:29:11 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Contains the testcase and a README (8.60 MB, application/x-gzip)
2009-06-19 11:36 EDT, rpalermo
no flags Details

  None (edit)
Description rpalermo 2009-06-19 11:36:14 EDT
Created attachment 348677 [details]
Contains the testcase and a README

Description of problem:
gcc Seg faults and we do not understand why. We would like to know why we're getting the seg fault and how we might work around it.

More information is available in the README file in the attached tarfile.

Version-Release number of selected component (if applicable):
gcc version 4.1.2 20080704 (Red Hat 4.1.2-44)

How reproducible:
gcc -c gnocomp.c

Steps to Reproduce:
1.gunzip test.tar.gz
2.gtar -zf test.tar
3.cd test
4.gcc -c gnocomp.c
Actual results:
seg fault

Expected results:
clean compile

Additional info:
Comment 1 Jiri Pallich 2012-06-20 09:29:11 EDT
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.

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