[issue7424] segmentation fault in listextend during install

[Jon Buller]

Jon Buller <jon at bullers.net> added the comment:

Sorry to not be able to follow up for so long, but I was moving 
cross-country.

I was playing with the tests a bit and ended up trying this:

$ ./python -E -tt -d -v -W all ./Lib/test/regrtest.py -l -v -s test_builtin

Which resulted (after quite a bit of output) in this:

# /usr/pkgsrc/lang/python26/work/Python-2.6.4/Lib/tempfile.pyc matches 
/usr/pkgsrc/lang/python26/work/Python-2.6.4/Lib/tempfile.py
import tempfile # precompiled from 
/usr/pkgsrc/lang/python26/work/Python-2.6.4/Lib/tempfile.pyc
dlopen("/usr/pkgsrc/lang/python26/work/Python-2.6.4/build/lib.netbsd-5.99.24-sparc-2.6/fcntl.so", 
2);
import fcntl # dynamically loaded from 
/usr/pkgsrc/lang/python26/work/Python-2.6.4/build/lib.netbsd-5.99.24-sparc-2.6/fcntl.so
import thread # builtin
test_builtin
[1]   Segmentation fault      ./python -E -tt -d -v -W all 
./Lib/test/regrtest.py -l -v -s test_builtin

So, is this perhaps a bug either in Python's thread usage, or NetBSD's 
thread
library?  Is there an easy way to tell python to build without any threads,
even if configure finds the proper system include files and libraries?  Is
it as simple as "./configure --without-threads" when starting the build?
(I'm about to try that...)

Jon

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue7424>
_______________________________________