Segmentation Fault

Alexandre Oliva aoliva@redhat.com
Fri Sep 28 16:33:00 GMT 2001


On Sep 15, 2001, pocm@rnl.ist.utl.pt (Paulo J. Matos aka PDestroy) wrote:

> # make bootstrap
> <supressing uninteresting lines>
> gcc -c  -DIN_GCC    -g  -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wtraditional -pedantic -Wno-long-long  -DHAVE_CONFIG_H    -I. -I. -I../../gcc-3.0.1/gcc -I../../gcc-3.0.1/gcc/. -I../../gcc-3.0.1/gcc/config -I../../gcc-3.0.1/gcc/../include ../../gcc-3.0.1/gcc/final.c -o final.o
> In file included from ../../gcc-3.0.1/gcc/system.h:85,
>                  from ../../gcc-3.0.1/gcc/final.c:48:
> ../../gcc-3.0.1/include/safe-ctype.h:1: Internal error: Segmentation fault
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <URL: http://www.gnu.org/software/gcc/bugs.html > for instructions.
> make[2]: *** [final.o] Error 1

Do you get the smae error if you `make bootstrap' again?  It seems
not, because bootstrap-lean does exactly the same, but gets you a
different error.  This is most often an indication of faulty
hardware.  Some people report this kind of error in cases of excessive
overclocking, broken memory, broken caches, etc.  Other than fixing
the broken hardware, sometimes disabling the L2 cache helps, with a
corresponding performance penalty.

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist    *Please* write to mailing lists, not to me



More information about the Gcc-bugs mailing list