From: dlj0@ns1.cc.lehigh.edu (DAVID L. JOHNSON) Subject: Re: Compiler Internel error, help! Date: 14 Sep 1992 04:52:00 GMT
In article <1992Sep11.122706.2218@athena.mit.edu>, hammond@kwhpc.caseng.com (Kevin W. Hammond) writes:
>|
>| >
>| > >
>| > >
>| > > Dear Linuxers,
>| > >
>| > > I got the following message:
>| > >
>| > > "gcc: Internal compiler error: program cc1plus got fatal signal 11"
>| > >
>| > > followed by a core dump when I compile the test.cc program below:
>| > >
>| >
>| > I had similiar problems when I started corrupting my filesystem (not
>| > on purpose, mind you!) A reboot usually took care of the problem for me.
>| > I'm in the process of trying to rebuild my linux drive and verify it this
>| > was the cause (tis not easy backing up 40MB onto floppies!)
>| >
>|
>| I think it's the problem of gcc, rather than the file system. The
>| SEGV problem occurs when we write some C++ code that makes gcc
>| choke. I tried the same code on the Sparc, the result is the same.
>|
>|
>
>Interesting. I had the problem when not even compiling a C++ program.
>All sorts of things started get SEGV's such as su, elm, reboot, etc.
>
>-kwh-
>--
>Kevin W. Hammond
>hammond@kwhpc.caseng.com
>
> "99.9% FAT Free"
>
> CASE Engineering * 575 W. Madison #1601 * Chicago, IL 60661 * (312)902-2161
I had these problems, too. But when I replaced some of the RAM they went
away. I suspect hardware, specifically RAM parity failure, rather than
software, especially when many programs cause the problem. I have had no
trouble with this, even compiling using X and playing games while the
compiler churned, since the RAM was replaced.
This gcc really hammers the RAM, and even problems that don't show up under
testing programs (like mine didn't) still cause these problems. I hope your
machine is still under warrantee.
>
-- Sincerely,David L. Johnson ID: dlj0@ns1.cc.lehigh.edu Christmas-Saucon Hall #14, rm 211 Department of Mathematics
Lehigh University Telephone: 215-758-3759 (office)