On Sat, 23 Jun 2001, James Henstridge wrote:
> I haven't been able to reproduce this problem (it exits normally for me).
> I haven't updated my copy of gtk today, but I doubt anything of interest
> has changed there.
This only happens when I omit --disable-threads from my configure line. If
I allow threads, boom. (As you have pointed out below, it matters).
> The bug appears to be caused by dereferencing a NULL python thread state
> variable. I don't know why that would occur.
I'm starting to think it's lack of pthread linked into someone, though I
can't say who. If you could, i'd like you to send in a paste of your ldd
output for /usr/local/lib/libgtk-1.3* and /usr/local/lib/libglib-1.3*
(maybe /usr/local/lib/libg* is in order, huh? :-)
Is there another way I can track this down?
Take care,
--
/\/\ Christian Reis, Senior Engineer, Async Open Source, Brazil
~\/~ http://async.com.br/~kiko/ | [+55 16] 274 4311
_______________________________________________
pygtk mailing list [EMAIL PROTECTED]
http://www.daa.com.au/mailman/listinfo/pygtk
