sig11 Error, probably not hardware-induced
Roman Legat
Roman.Legat@stud.uni-hannover.de
Sat Sep 18 08:32:00 GMT 1999
Hi!
I'd like to report a compiler-crash when building gcc-2.95.1 .
It is a sig11-error (see below). I read the Sig11-FAQ from
www.bitwizard.nl and following the text it is probably not a
hardware-problem.
My system is a i586-pc-linux-gnu with a AMD K6-2-400 (stepping 0c) .
The linux is the Suse-Distribution 6.2, the kernel is 2.2.12 .
My compiler was gcc-2.7.2.3. Because building gcc-2.95.1 failed at
my machine, I built it at a friends machine (where it worked), so now
I run gcc-2.95.1 . The error occurs with both versions.
This is what I did :
rocko@mazzy:/tmp> tar xfz gcc-2.95.1.tar.gz
rocko@mazzy:/tmp> mkdir objdir
rocko@mazzy:/tmp> cd objdir
rocko@mazzy:/tmp/objdir> ../gcc-2.95.1/configure
rocko@mazzy:/tmp/objdir> make bootstrap
Then it would run and compile some files, until this compiler output:
echo "int xxy_us_dummy;" >tmp-dum.c
./xgcc -B/usr/local/i586-pc-linux-gnu/bin/ -B./
-I/usr/local/i586-pc-linux-gnu/include -S tmp-dum.c
xgcc: Internal compiler error: program cpp got fatal signal 11
make[2]: *** [s-under] Error 1
make[2]: Leaving directory `/tmp/objdir/gcc'
make[1]: *** [bootstrap] Error 2
make[1]: Leaving directory `/tmp/objdir/gcc'
make: *** [bootstrap] Error 2
The compiler ALWAYS crashes at this point when I run it again, even when
I use 'make' instead of 'make bootstrap'. (I don't know if there is a
difference between these two at this stage)
Like proposed in the Sig11-FAQ, i ran
root@mazzy:/tmp/objdir> dd if=/dev/hda of=/dev/null bs=1024k count=65
rocko@mazzy:/tmp/objdir> make bootstrap
to cause the files to be read again from disk. This resulted in the
described error, too.
I know that you are really busy, but I'd be glad to know, what you
think of this. I didn't know which files to attach, so if you need more
information, tell me what you need.
Regards,
Roman Legat
--
Roman Legat
email: roman@stud.uni-hannover.de
[ stud means student ;) ]
Anything is good, if it's made of chocolate
More information about the Gcc-bugs
mailing list