From: johnhm@vaxc.cc.monash.edu.au Subject: GCC and the 'signal 11' problem, HELP! Date: 1 Jun 1992 17:54:51 +1000
I seek clarification concerning the "internal compiler error" problem
I have been plagued with ever since starting out with GCC 2.1.
The error (from memory) goes something like this :
...
<Register dump>
...
Internal compiler error. cc1 got signal 11
The compiler will mostly bomb out with the above message when compiling
from a Makefile.
It may not reliably bomb out on any particular source file,
however sometimes it will get "stuck" on a file.
The offending file will sometimes get through compiling by re-running the
makefile, although often typing the compile command line manualy is necessary.
Failures are more likely to occur after Linux has been worked heavily,
which suggests the problem is related to memory fragmention.
The above points are valid with linux version .95a .96 and .96a
and with GCC 2.1-2.12b (excludeing 2 I skipped).
My machine configuration is :
386DX with ETEQ chipset (tiawanese clone)
8Mb memory
64k cache
Tsenglab 4000 video
Adaptec 1542B SCSI adaptor
MFM HD controler
The fact that only a few people have reported the problem makes it sound
like a hardware problem however I have read in gnu.gcc.help that people using
machines other than PC's have seen this error.
Can anyone say something authoritive on this problem (hlu ?).
I have had other possibly related problems with 2.12b. The assembly stage
will sometimes read garbage characters from somewhere (the file generated
from cc1?) and sometimes the compiler will bomb out with "segmention fault".
This didn't happen with previon versions.
--John H. Morris E-mail: johnhm@vaxc.cc.monash.edu.au Monash University Computer Centre Phone: +61 3 5654763 Wellington Road, FAX: +61 3 5654746 Clayton 3168, Australia.