From owner-freebsd-current@FreeBSD.ORG Sun Aug 31 09:24:57 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 D98EA16A4BF for ; Sun, 31 Aug 2003 09:24:57 -0700 (PDT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id CB1C643FF9 for ; Sun, 31 Aug 2003 09:24:56 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) h7VGOuin008378; Sun, 31 Aug 2003 09:24:56 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)h7VGOtE7008377; Sun, 31 Aug 2003 09:24:55 -0700 (PDT) Date: Sun, 31 Aug 2003 09:24:55 -0700 From: Steve Kargl To: "Alastair G. Hogge" Message-ID: <20030831162455.GA8332@troutmask.apl.washington.edu> References: <200308311952.15537.agh@tpg.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200308311952.15537.agh@tpg.com.au> User-Agent: Mutt/1.4.1i 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: Sun, 31 Aug 2003 16:24:58 -0000 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? However, your last sentence in the above quoted paragraph, suggests that you have bad memory or a heating problem or a suspect power supply. -- Steve