> > That '2419 Segmentation fault gcc ....' looks bad. gcc only > segfaults on compiler bugs or hardware errors in my experience. Of > course being gcc 4.0.x compiler bugs are entirely possible. > > On the other hand the fact it is _not_ happening the same place each > time rather makes the hardware error much more likely. >
:-( > If you can do make clean and then build it and have it fail the same > place 3 or 4 times in a row, then submit a bugreport on gcc-4.0. > If it doesn't fail the same place each of those times, start swapping ram, > cpu, etc, until you find the faulty hardware. > The fault occurs at different places... I already did a complete pass with "memtest86+"; it didn't report a single memory error. What and how should I test next? Do I just unplug one of the processors? Is there some other diagnostics tool which I can run? Gilles -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]