Re: (g)cc errors

["Dom De Vitto" <dom@DeVitto.com>]

Hardware problem
This is so common that it's in the FAQ, and the same happens for
Linux/bsds etc. There is even a "signal 11" FAQ !

Searching for "signal 11 gcc" should come up with lots, but it's
most likely a memory fault, otherwise you'll be having fun tracking
it down.

Basically signal 11 means that the program did a real bad thing -
tried to access memory it doesn't "own".  Unless the program is being
developed, this never normally happens.  It does happen when 
memory gets corrupted on the way from the memory to the CPU (on when
in the memory, or in the CPU).  The memory did contain the address
or a "valid" place in memory, but got corrupted into an "invalid" one.
The OS then balks with "You can't access that memory!" - Signal 11.

Swapping memory chips out until the problem goes away is the most
common approach, but the problem could be with the CPU, mobo or
anything else that could cause dodgyness.

Dom
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Dom De Vitto                                       Tel. 07855 805 271
http://www.devitto.com                         mailto:dom@devitto.com
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

-----Original Message-----
From: owner-misc@openbsd.org [mailto:owner-misc@openbsd.org] On Behalf Of
Bram Van Dam
Sent: Sunday, November 02, 2003 2:18 PM
To: misc@openbsd.org
Subject: (g)cc errors

Greetings,

I installed OpenBSD 3.4 on a relatively old (K6-2 233) machine quite
recently and I'm having some difficulties while compiling applications.
(Not just the ports, but pretty much anything I compile).

Every now and then (sometimes up to four times while compiling one
application) I get the following error:

cc: Internal compiler error: program cc1 got fatal signat 11
*** Error code 1

Needless to say that the compiler then halts.

If I type 'make' again the compiler will continue where it left off, but
it's still quite annoying, plus I'm getting core dumps in a few applications
compiled in this unhealthy way.

Is this a known problem? Can it be hardware related? Or better yet, can it
be fixed?

  - Bram