C++ extension module crashes on Solaris

[Steven E. Harris]

I'm trying to write a simple Python extension module using the CXX
kit. When I attempt to import my compiled module, Python dies as
follows:

Python 1.5.2 (#9, May 18 2000, 13:45:16)  [GCC 2.95.2 19991024 (release)] on sunos5
Copyright 1991-1995 Stichting Mathematisch Centrum, Amsterdam
>>> import seh_test
Fatal Python error: PyThreadState_Get: no current thread
Abort (core dumped)


The stack trace looks like this:


> gdb python core
GNU gdb 4.18
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "sparc-sun-solaris2.5.1"...
Core was generated by `python'.
Program terminated with signal 9, Killed.
Reading symbols from /usr/lib/libsocket.so.1...done.
Reading symbols from /usr/lib/libnsl.so.1...done.
Reading symbols from /usr/lib/libdl.so.1...done.
Reading symbols from /usr/lib/libpthread.so.1...done.
Reading symbols from /usr/lib/libthread.so.1...done.
Reading symbols from /usr/lib/libm.so.1...done.
Reading symbols from /usr/lib/libc.so.1...done.
Reading symbols from /usr/lib/libintl.so.1...done.
Reading symbols from /usr/lib/libmp.so.1...done.
Reading symbols from /usr/lib/libw.so.1...done.
Reading symbols from /users/sharris/temp/CXX-4.2/seh_test/./seh_test.so...done.
#0  0xef6a2a58 in __sigprocmask () from /usr/lib/libthread.so.1
(gdb) where
#0  0xef6a2a58 in __sigprocmask () from /usr/lib/libthread.so.1
#1  0xef69a6b8 in _resetsig () from /usr/lib/libthread.so.1
#2  0xef69a174 in _sigon () from /usr/lib/libthread.so.1
#3  0xef69ca50 in _thrp_kill () from /usr/lib/libthread.so.1
#4  0xef5ba6f0 in abort () from /usr/lib/libc.so.1
#5  0xeec4bb0c in Py_AtExit (func=0xeec9c198 <tinytens+21896>) at pythonrun.c:1036


I compiled Python with the '--with-thread' switch enabled on Solaris
2.5.1, hoping to pull in POSIX threading support.

Does this look like a familiar problem? I couldn't find any proper
answers in the archives.

-- 
Steven E. Harris
Primus Knowledge Solutions, Inc.
http://www.primus.com