gcc segfault

[yannleguennec]

Hi there,

Since some weeks, my gcc seems to be unable to compile big packages properly
(gcc itself, mysql postgres, X11, etc...). it causes segmentation fault for no reason
but oddly works for small packages.

I thought of a hardware problem, but a night running memtest86+
does show no errors at all.

Could it be my gcc has not been build properly ?

As gcc uses itself to upgrade, it does not work.
Is there a way do install a binary gcc to try to get out of this ?

any ideas ?

Cheers,
Yann.

PS: the config is pretty old : AMD K6-2 300MHz with 128Mo RAM
the running version of GCC gives 'gcc version 3.4.3 (Gentoo Linux 3.4.3, ssp-3.4.3-0, pie-8.7.6.5)'
the CFLAGS is "-march=k6-2 -O3 -pipe" in make.conf, changing it to -mcpu or -O0 does not improve much.

[yaneurabeya]

It could also be the CPU dying or an issue with your harddisk =\... What's the exact error message?

[yannleguennec]

I will test the disk tonight, but I have to get off the Net to do that ;-)
Really hope that not that... If it's the CPU, that will just force me
to upgrade the whole thing... ;-)

Here is what I get when I emerge -u gcc :

/var/tmp/portage/gcc-3.4.3.20050110/work/gcc-3.4.3/gcc/combine.c: In function `combine_simplify_rtx':
/var/tmp/portage/gcc-3.4.3.20050110/work/gcc-3.4.3/gcc/combine.c:4645: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:https://bugs.gentoo.org/> for instructions.
The bug is not reproducible, so it is likely a hardware or OS problem.
make[2]: *** [combine.o] Error 1
make[2]: Leaving directory `/var/tmp/portage/gcc-3.4.3.20050110/work/build/gcc'
make[1]: *** [stageprofile_build] Error 2
make[1]: Leaving directory `/var/tmp/portage/gcc-3.4.3.20050110/work/build/gcc'
make: *** [profiledbootstrap] Error 2

!!! ERROR: sys-devel/gcc-3.4.3.20050110 failed.
!!! Function gcc_do_make, Line 1079, Exitcode 2
!!! make failed with profiledbootstrap
!!! If you need support, post the topmost build error, NOT this status message.

Yann.

[anxt]

I am having a similar problem. I replaced the old cratered (200 gb maxtor) hard drive and ghosted the stuff over. well i tried to emerge -e system to replace corrupted system files and it puked i figured well maybe some libs are hooped.

reinstalled from 2004.3 x86 minimal emerged sytem and a lot of world and the it puked. first on kdepim, the on emerge -e system (on perl)

(do i ever want to hit my computer)

brand new processor, i already tried another old one (2x AthlonXP 1800 stepping 1, stepping 6) and replaced with sempron 3000, ram tests OK. haven't run maxtor utils on new hd.

Am I ever getting frustrated, i have been trying to sort this out for two weeks, and even did a fresh install, which i hadn't done for 2 years, and was hoping never to

*shrug*

probably NOT the hardware, unless my board is doing some weird flakiness

ran memtest86+ for like 12 hours no problems.

so far

1 new HD,
3 processors,
ram tests good (2 months old)
power supply 450w so no saggy supplies (just another shot in the dark)
mobo is one month old

currently switched to gcc 3.4.3

now i am trying:

[yaneurabeya]

I understand the issue at hand because similarly I have a 160 Gb Seagate that went out after the first 2 weeks I used it due to improperly shutting it down once (this was caused by stresses on the disk and so forth and it just had to fail near the MBR =\...). At least they have 5 year warranties on these things.

[zerojay]

Just because memtest86 didn't give you any errors doesn't mean that there isn't a problem with your RAM still. I'd run it for at least 48 hours to be sure.

[anxt]

That is a good word, I thought so too (ie memtest saying it is OK). I popped in two sticks of 128mb ddr and I am testing to see if it pukes on those. Other than that it is mobo or some kind of software weirdness i can't figure out. Probably the ram though. Already got 1 bad stick from this batch. I should probably just buy some "name brand" ram

I ran mprime -t on it for a few hours, it was OK but when I got home my "computer had stop responding (tm)"

[yaneurabeya]

Due to mass production many RAM sticks and (more notoriously) hard drives fail within the first couple months of use I've heard. So since my hd failed I'm going to consider buying a nice warranty unless I buy Seagate.