From owner-freebsd-questions@FreeBSD.ORG Wed Feb 14 21:26:54 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B249116A420 for ; Wed, 14 Feb 2007 21:26:54 +0000 (UTC) (envelope-from rob@redbrick.dcu.ie) Received: from hawk.dcu.ie (mail.dcu.ie [136.206.1.5]) by mx1.freebsd.org (Postfix) with ESMTP id 75A6113C46B for ; Wed, 14 Feb 2007 21:26:54 +0000 (UTC) (envelope-from rob@redbrick.dcu.ie) Received: from deathray.redbrick.dcu.ie (136.206.15.3) by hawk.dcu.ie (7.3.120) id 45AD34A8003B62CD for freebsd-questions@freebsd.org; Wed, 14 Feb 2007 21:26:53 +0000 Received: from login.redbrick.dcu.ie ([2001:770:107:15::50] helo=murphy.redbrick.dcu.ie ident=Debian-exim) by deathray.redbrick.dcu.ie with esmtp (Exim 4.50) id 1HHReP-0007tU-Qc for freebsd-questions@freebsd.org; Wed, 14 Feb 2007 21:26:53 +0000 Received: from rob by murphy.redbrick.dcu.ie with local (Exim 4.60) (envelope-from ) id 1HHReP-0007hb-L6 for freebsd-questions@freebsd.org; Wed, 14 Feb 2007 21:26:53 +0000 Date: Wed, 14 Feb 2007 21:26:53 +0000 From: Rob Gallagher To: freebsd-questions@freebsd.org Message-ID: <20070214212653.GA21536@murphy.redbrick.dcu.ie> References: <20070214115545.GA19424@murphy.redbrick.dcu.ie> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.11 Subject: Re: Compile of Python 2.4.4 core dumps 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: Wed, 14 Feb 2007 21:26:54 -0000 Hi Niclas, On Wed, Feb 14, 2007 at 01:54:36PM +0100, Niclas Zeising wrote: > > Usually if a compile coredumps it's due to faulty memory or other > hardware. Might be good to check that first. Especially since it > worked flawlessly on another box. > HTH > //Niclas > Thanks for the reply. I'm unsure if it's down to faulty memory because the machine is very new and I don't get core dumps when compiling or running any other software. Also, in my experience hardware faults have caused compiles to behave erraticlly, ie: bombing out at random stages in the build process - this core dump always occurs at exactly the same point (compilation of the curses module). ps: sorry about not wrapping my lines in the original post! ;-) rg -- "We have an announcement to make... uh... on July 4th of this year, America will blow up the moon."