C++ extension module crashes on Solaris

[Guido van Rossum]

> > I suggest posting some source code if you expect help.  It's probably a
> > simple
> > bug in your code but it's hard to spot without looking at your code.
> >
> > You seem concerned about threads.  are you starting threads in your C code
> > that
> > will call on Python?  If so, that's where the problem is -- you have to
> > study
> > the C/API docs carefully regarding the interpreter lock.
> >
> No offense Guido, but you are probably completely off base.
> I'll put money it's a shared library problem.
> I remember someone running into this problem on SunOS before, and i've
> personally run into it on FreeBSD.
> In fact, if you just compile on freebsd-current, with the modules shared,
> without using the version of python in the FreeBSD ports system, and then do
> something as simple as "import time" or "import zlib" (IE import a shared
> module), you'll get the same error.

That's very well possible.  Is there an entry in the Python Bugs
Database for this yet?

> As soon as i wake up, if someone hasn't posted the fix, i'll do it (It's
> very late, it escapes my brain).

I'd be most delighted.

(Note that for Py1.6, we've restructured the shared lib code -- if you
have a patch, it would be great if you could prepare one for 1.6 and
post it to patches at python.org...)

--Guido van Rossum (home page: http://www.python.org/~guido/)