Date: Fri, 16 Feb 2007 01:13:24 +0100 From: =?ISO-8859-1?Q?Bj=F8rn_Erik_Sj=F8tun?= <bjoernerik@gmail.com> To: freebsd-questions@freebsd.org Subject: Re: Compile of Python 2.4.4 core dumps Message-ID: <45D4F724.6060301@gmail.com> In-Reply-To: <20070214212653.GA21536@murphy.redbrick.dcu.ie> References: <20070214115545.GA19424@murphy.redbrick.dcu.ie> <bc292860702140454i323cb019xac3f6df3c7410044@mail.gmail.com> <20070214212653.GA21536@murphy.redbrick.dcu.ie>
next in thread | previous in thread | raw e-mail | index | archive | help
Rob Gallagher wrote: > 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). > I am experiencing the same problem (also running 6.2-RELEASE), so your hardware is not the cause. I'm afraid I don't have any helpful ideas, though. Bjørn
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45D4F724.6060301>