From owner-freebsd-current@FreeBSD.ORG Mon Sep 1 05:48:45 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 E00FD16A4BF for ; Mon, 1 Sep 2003 05:48:45 -0700 (PDT) Received: from mail2.tpgi.com.au (mail.tpgi.com.au [203.12.160.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5B3E143FE0 for ; Mon, 1 Sep 2003 05:48:42 -0700 (PDT) (envelope-from agh@tpg.com.au) Received: from 192.168.0.2 (220-244-72-6.tpgi.com.au [220.244.72.6]) by mail2.tpgi.com.au (8.12.9/8.12.9) with ESMTP id h81CmbVb026401 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Mon, 1 Sep 2003 22:48:38 +1000 From: "Alastair G. Hogge" To: Steve Kargl Date: Mon, 1 Sep 2003 22:48:43 +1000 User-Agent: KMail/1.5.3 References: <200308311952.15537.agh@tpg.com.au> <20030831162455.GA8332@troutmask.apl.washington.edu> In-Reply-To: <20030831162455.GA8332@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200309012248.43597.agh@tpg.com.au> X-Kaspersky-Antivirus: Passed 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 12:48:46 -0000 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 :-( -Al