From owner-freebsd-current@FreeBSD.ORG Mon Sep 1 06:03:00 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6B98C16A4BF for ; Mon, 1 Sep 2003 06:03:00 -0700 (PDT) Received: from mta8.adelphia.net (mta8.adelphia.net [68.168.78.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 66D3B43FE3 for ; Mon, 1 Sep 2003 06:02:59 -0700 (PDT) (envelope-from wmoran@potentialtech.com) Received: from potentialtech.com ([24.53.179.151]) by mta8.adelphia.net (InterMail vM.5.01.05.32 201-253-122-126-132-20030307) with ESMTP id <20030901130300.NOGB19763.mta8.adelphia.net@potentialtech.com>; Mon, 1 Sep 2003 09:03:00 -0400 Message-ID: <3F534382.5010002@potentialtech.com> Date: Mon, 01 Sep 2003 09:02:58 -0400 From: Bill Moran User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3) Gecko/20030429 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Alastair G. Hogge" References: <200308311952.15537.agh@tpg.com.au> <20030831162455.GA8332@troutmask.apl.washington.edu> <200309012248.43597.agh@tpg.com.au> In-Reply-To: <200309012248.43597.agh@tpg.com.au> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: buildworld seg faulting. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Sep 2003 13:03:00 -0000 Alastair G. Hogge wrote: > On Monday, 01 September 2003 02:24, Steve Kargl wrote: > >>On Sun, Aug 31, 2003 at 07:52:15PM +1000, Alastair G. Hogge wrote: >> >>>Hello list, >>> >>>For the past couple of weeks I've been tyring to keep my system up to >>>date with cvsup. However, when ever I run a buildworld I get problems >>>with gcc (I think it's gcc). I've tried nuking /usr/obj and running "make >>>clean" many tims before each build but this doesn't help. What I've >>>noticed is that the seg fault doesn't occur in the same place. >> >>There isn't enough context in the error messages you reported. >>Are you using the -j option during your buildworld? > > No. just plain old "make buildworld" i did also try -j3 > > >>However, your last sentence in the above quoted paragraph, >>suggests that you have bad memory or a heating problem or a >>suspect power supply. > > Ahhh. I don't like the sound of that. > > Is there something else I'm leaving out. I really hope it isn't memory I sold > my thumbs to get 512megs of Corsair XSM :-( Download memtest86 and let it run for a couple of hours. If you see any errors at all, try and get that memory replaced under warranty. -- Bill Moran Potential Technologies http://www.potentialtech.com