Segfault on gcc on bignum.c

ruby-talk
1

with
[167 cc1@tom ~/install/ruby]$ ./configure --prefix=$HOME/usr --enable-install-doc --enable-pthread

I got -

[163 cc1@tom ~/install/ruby]$ make
gcc -g -O2 -I. -I. -I/home/cc1/usr/include -c bignum.c
bignum.c: In function `rb_uint2big':
bignum.c:153: internal error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://bugzilla.redhat.com/bugzilla/> for instructions.
make: *** [bignum.o] Error 1

[164 cc1@tom ~/install/ruby]$ gcc -v
Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux
Thread model: posix
gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-20)

This appears to be a bug in gcc but anyone have any ideas with this? The machine has a fair amount of custom hardware and stuff that may be part of the problem, but anyone else have a problem like this before?

Charles Comstock

2

Are you able to reproduce the error? gcc segfaults are typically
indicative of a hardware problem.

Sam

···

On Wed, 30 Jun 2004 16:22:53 +0900, Charles Comstock <cc1@cec.wustl.edu> wrote:

This appears to be a bug in gcc but anyone have any ideas with this?
The machine has a fair amount of custom hardware and stuff that may be
part of the problem, but anyone else have a problem like this before?

3

Sam Stephenson wrote:

···

On Wed, 30 Jun 2004 16:22:53 +0900, Charles Comstock <cc1@cec.wustl.edu> wrote:

This appears to be a bug in gcc but anyone have any ideas with this?
The machine has a fair amount of custom hardware and stuff that may be
part of the problem, but anyone else have a problem like this before?

Are you able to reproduce the error? gcc segfaults are typically
indicative of a hardware problem.

Sam

Every time I type make it segfaults. It's consistant in that respect. I don't have another machine I can test that version of gcc on though if that's what you mean to see if it's a problem with that machine.

Charlie

4

Charles Comstock wrote:

Sam Stephenson wrote:

This appears to be a bug in gcc but anyone have any ideas with this?
The machine has a fair amount of custom hardware and stuff that may be
part of the problem, but anyone else have a problem like this before?

Are you able to reproduce the error? gcc segfaults are typically
indicative of a hardware problem.

Sam

Every time I type make it segfaults. It's consistant in that respect. I don't have another machine I can test that version of gcc on though if that's what you mean to see if it's a problem with that machine.

Charlie

Hmm never mind, that's what happened last night, but now it makes fine. Very strange.

Charlie

···

On Wed, 30 Jun 2004 16:22:53 +0900, Charles Comstock >> <cc1@cec.wustl.edu> wrote: