From owner-freebsd-questions@FreeBSD.ORG Mon Sep 19 22:12:55 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 CB39C16A41F for ; Mon, 19 Sep 2005 22:12:55 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from smtpout.mac.com (smtpout.mac.com [17.250.248.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3C18843D45 for ; Mon, 19 Sep 2005 22:12:55 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from mac.com (smtpin07-en2 [10.13.10.152]) by smtpout.mac.com (Xserve/8.12.11/smtpout01/MantshX 4.0) with ESMTP id j8JMCsDP026822; Mon, 19 Sep 2005 15:12:54 -0700 (PDT) Received: from [10.1.1.209] (nfw1.codefab.com [199.103.21.225]) (authenticated bits=0) by mac.com (Xserve/smtpin07/MantshX 4.0) with ESMTP id j8JMCp1u010200; Mon, 19 Sep 2005 15:12:52 -0700 (PDT) In-Reply-To: <810a540e050919150428c0cea1@mail.gmail.com> References: <810a540e05091818065f10356e@mail.gmail.com> <444q8gdd8g.fsf@be-well.ilk.org> <810a540e050919150428c0cea1@mail.gmail.com> Mime-Version: 1.0 (Apple Message framework v734) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Charles Swiger Date: Mon, 19 Sep 2005 18:12:35 -0400 To: pergesu@gmail.com X-Mailer: Apple Mail (2.734) Cc: freebsd-questions@freebsd.org Subject: Re: Segmentation fault when building kdelibs X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Sep 2005 22:12:55 -0000 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? Pretty much what was quoted above. :-) 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. -- -Chuck