From owner-freebsd-questions@FreeBSD.ORG Mon Sep 19 22:16:29 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 327BF16A420 for ; Mon, 19 Sep 2005 22:16:29 +0000 (GMT) (envelope-from pergesu@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8EB3E43D62 for ; Mon, 19 Sep 2005 22:16:27 +0000 (GMT) (envelope-from pergesu@gmail.com) Received: by zproxy.gmail.com with SMTP id 40so90733nzk for ; Mon, 19 Sep 2005 15:16:27 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=XTN1oIcRDCYw5mTd/Eo3bDrQZRvzYHVzgaOIB0wWIZmUC51MWcYMf+rJ/U9oyu6V9L2XBwrHUHRolUrDhGHNVWtWT65EY7slPrEgR1U1Hv1RfLjpI3YvWsdl4awaZ5Sr5VIuQg09/WYIF0R1AUgF/t5kzo+XC2pkgAmWbksygGo= Received: by 10.37.21.12 with SMTP id y12mr3351231nzi; Mon, 19 Sep 2005 15:16:26 -0700 (PDT) Received: by 10.36.48.17 with HTTP; Mon, 19 Sep 2005 15:16:26 -0700 (PDT) Message-ID: <810a540e05091915165d4a2041@mail.gmail.com> Date: Mon, 19 Sep 2005 16:16:26 -0600 From: Pat Maddox To: Charles Swiger , FreeBSD Questions In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <810a540e05091818065f10356e@mail.gmail.com> <444q8gdd8g.fsf@be-well.ilk.org> <810a540e050919150428c0cea1@mail.gmail.com> Cc: Subject: Re: Segmentation fault when building kdelibs X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pergesu@gmail.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Sep 2005 22:16:29 -0000 On 9/19/05, Charles Swiger wrote: > On Sep 19, 2005, at 6:04 PM, Pat Maddox wrote: > >> The obvious question is: does it always fail at the same point? If > >> not, then it's almost certainly a hardware problem. If it does, then > >> a bit more information on your system would be needed, including how > >> you updated the ports skeletons, and whether you tried updating them > >> again since you first saw the problem. And if you aren't already, > >> try > >> using the system compiler to build the port. > > > > I've had a couple people suggest that it may be a hardware problem - > > what should I be looking for? >=20 > Pretty much what was quoted above. :-) >=20 > If you run the same build twice, does the compiler crash at the same > place, or in a different place? If the crash happens somewhere else > each time, it's probably hardware. >=20 > -- > -Chuck >=20 >=20 Happens in different spots, so I guess it's a hardware problem. But what exactly am I looking for? Is it bad ram, a bad disk? How do I find out what's messed up?