Date: Wed, 14 Feb 2007 13:54:36 +0100 From: "Niclas Zeising" <niclas.zeising@gmail.com> To: "Rob Gallagher" <rob@redbrick.dcu.ie> Cc: freebsd-questions@freebsd.org Subject: Re: Compile of Python 2.4.4 core dumps Message-ID: <bc292860702140454i323cb019xac3f6df3c7410044@mail.gmail.com> In-Reply-To: <20070214115545.GA19424@murphy.redbrick.dcu.ie> References: <20070214115545.GA19424@murphy.redbrick.dcu.ie>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2/14/07, Rob Gallagher <rob@redbrick.dcu.ie> wrote: > Hi, > > Upgrading to latest version of python24 port (2.4.4), the compilation process > core dumps shortly after it begins. Here is the output leading up to the core > dump: > > cc -DNDEBUG -O2 -fno-strict-aliasing -pipe -D__wchar_t=wchar_t -DTHREAD_STACK_SIZE=0x20000 -fPIC -fno-strict-aliasing -I. -I/usr/ports/lang/python24/work/Python-2.4.4/./Include -I/usr/local/include -I/usr/ports/lang/python24/work/Python-2.4.4/Include -I/usr/ports/lang/python24/work/Python-2.4.4 -c /usr/ports/lang/python24/work/Python-2.4.4/Modules/_cursesmodule.c -o build/temp.freebsd-6.2-RELEASE-i386-2.4/_cursesmodule.o > cc -shared -pthread -O2 -fno-strict-aliasing -pipe -D__wchar_t=wchar_t -DTHREAD_STACK_SIZE=0x20000 build/temp.freebsd-6.2-RELEASE-i386-2.4/_cursesmodule.o -L/usr/local/lib -lncurses -o build/lib.freebsd-6.2-RELEASE-i386-2.4/_curses.so > Segmentation fault (core dumped) > > I'm running 6.2-RELEASE. I've upgraded another 6.2 box to python 2.4.4 without a problem, so I'm thinking the issue must lie with something on this system. > > rg > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bc292860702140454i323cb019xac3f6df3c7410044>