On Sat, 14 Feb 2004 11:00:35 +0100, PiotrAF wrote:

>On Sat, 14 Feb 2004 03:15:08 +0100, Andreas Klauer wrote:
>
>>>> Looks like you could do with down-clocking your system.
>>>
>
>Still don't know what was meant by that
>
>> Random segfaults like that indicate that there's something
>> wrong with your hardware.
>
>Yes, I've herd it a million times. Strange that it happens on most of my
>machines and even after changing that hardware. Besides, It's not a
>problem and a hint to others. There is no harm in "||" even if you have a
>superhardware - it will always stop if it finishes the emerge the first
>time, and my life with gentoo would have been much easier a year ago if
> someone instead of telling me I have broken hardware gave me such hint

I had an overclocked athlon xp and whilst I didn't see segmentation faults
whilst compiling I did see cpu errors when encoding video (only from dmesg
not encoder stderr). Some were recoverable, some not. After dropping the
multiplier these errors ceased completely. With intensive compiling you're
quite likely to get similar problems. I know very little about the
compiling process, but I believe it's possible to generate flawed
executables without seeing segfaults or problems that halt the compile.