Thorsten,
I surely hope notâ•œ this looks more like a hardware issue, possibly faulty RAM, to me. (Never saw the ╲The bug is not reproducible╡ blurb beforeâ•œ)
I've seen that one before - it's been there pretty much since the stone ages. gcc does exercise memory more thoroughly than anything else, and hardware faults that went undetected otherwise got triggered.
That's all ancient history though (RAM starved machines were qute commonn before memory got cheap). Might not matter much now. Then again, we're dealing with historic HW here.
I can try and run the binary or binaries faulting on my 060 to make sure. Same on ARAnyM.
Cheers, Michael
Well, as I said: I can run some memory testing tomorrow. This, of course, doesn't guarantee that the memory is without any faults, if nothing pops up. Only if something is found, then it's sure that the memory is faulty. But what if the test won't show memory issues? I'll start another try on a second machine in the meanwhile. Schroot segfaults there as well, but I can try the same on my third machine. I hardly doubt that the memory is causing the same issues in 3 different machines. That's why I believe it's a toolchain problem...-- Ciao... // Fon: 0381-2744150 Ingo \X/ http://blog.windfluechter.net gpg pubkey: http://www.juergensmann.de/ij_public_key.asc -- To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.orgwith a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/35FFF349-D8BC-4C1D-BD10 -93244747f...@2012.bluespice.org
-- To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ee179dc8fed0e8801c50a2ff9170...@biophys.uni-duesseldorf.de
