Date: Thu, 17 Aug 2006 18:09:56 +0200 From: Mischa Peters <freebsd@high5.nu> To: Alex Zbyslaw <xfb52@dial.pipex.com> Cc: freebsd-questions@freebsd.org Subject: Re: FreeBSD 6.1 buildworld segfault on gcc Message-ID: <A7E3AA67-51BD-4861-BA22-D48422524776@high5.nu> In-Reply-To: <44E49084.8070502@dial.pipex.com> References: <025B38CC-B003-4C31-AE23-07190E7D0212@high5.nu> <44E4889F.7040902@dial.pipex.com> <7ADCA268-4E9A-4FCD-A5C7-E29C94C1CC73@high5.nu> <44E49084.8070502@dial.pipex.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>>> Does it always segfault in the same place? If not then faulty >>> memory is your number one suspect. For that try memtest86+ >>> (google for it and burn a CD), or just try pulling memory sticks >>> and seeing if the problem goes away (but beware static). >> >> >> It's always in the same place, with the same message. :( > > Well, that doesn't rule out memory trouble, but it's not very > definitive for anything else. :-( > > Have you tried deleting everything under /usr/obj and trying > again? Worth a shot but if nothing comes of it and no better > suggestions arrive, test that memory! > > rm -fr /usr/obj/* > whatever make buildworld and buildkernel stuff you did. I have tried everything already in regards to a clean build environment. make clean, make cleandir, make cleanworld... refetching the source. I will try again in a couple of days... see if that makes any difference. I will test the memory, you never know. Thanx for your help! Mischa
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A7E3AA67-51BD-4861-BA22-D48422524776>