Bug 147561 - g++: Internal error: Segmentation fault (program cc1plus)
Summary: g++: Internal error: Segmentation fault (program cc1plus)
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gcc
Version: 3
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-02-09 09:28 UTC by Ambey Govenkar
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-02-28 16:56:45 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Ambey Govenkar 2005-02-09 09:28:53 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041020
Firefox/0.10.1

Description of problem:
The g++ compiler crashes, with segmentation fault, while compiling c++
source file. Doesn't crash while compiling C source file.



Version-Release number of selected component (if applicable):
gcc-c++-3.3.3-7

How reproducible:
Always

Steps to Reproduce:
1.compile a C++ file, on command line:
   g++ -g -Wall -c source_file.cpp
    

Actual Results:  g++ crashed with segmentation fault

Expected Results:  To compile the source file, or to give syntax errors.

Additional info:

Crashed consistently with some source files, but didn't crashed for
some other files.

Comment 1 Jakub Jelinek 2005-02-09 10:55:56 UTC
gcc-c++-3.3.3-7 is not FC3 compiler, but FC2 one.
You have not provided a testcase (usually the compiler driver preprocesses
the source and tells you where it is) nor the error messages it printed, so there
is nothing to do about it.  But unless it is reproduceable with FC3 compiler,
(3.4.[23]-RH), it will be either closed as CURRENTRELEASE or moved upstream,
as the compilers that we are maintaining long term are just GCC 3.2.3-RH and
GCC 3.4.3-RH (plus CVS HEAD) and FC2 is close to its EOL.

Comment 2 Jakub Jelinek 2005-02-28 16:56:45 UTC
If you have details, please reopen.


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