Python + threads + wxWindows = segfault, help!

[Greg Copeland]

Arg!  In my hurry to get this posted it seems that I left some
important information out.  I'm running Python 2.1 with wxPython
2.2.5 and wxWindows 2.2.7, though I get the same results with
2.2.5 as well.

The application design is using the parent for the GUI and
threads for communication.  Data is passed back and forth via
Python's Queue class.

Most of the segs that I get seemingly have to do with threads.
I think I'm the only SMP user on the project and oddly enough,
I think I'm the only user seeing issues like this.

Thanks again.  Any more ideas or tips would be wonderful!

Greg


aahz at panix.com (Aahz Maruch) writes:

> In article <m2y9rcq5b7.fsf at mouse.copelandconsulting.net>,
> Greg Copeland  <gtcopeland at earthlink.net> wrote:
> >
> >I'm working on a project that has a multithreaded wxPython
> >application.  I working on an SMP box.  Can anyone tell me
> >what might be causing this to happen?
> >
> >Fatal Python error: ceval: orphan tstate
> 
> If you're using Python 1.5.2, upgrade to Python 2.x; there's a thread
> bug in 1.5.2 with SMP combined with creating/destroying large numbers of
> threads.
> -- 
>                       --- Aahz  <*>  (Copyright 2001 by aahz at pobox.com)
> 
> Androgynous poly kinky vanilla queer het Pythonista   http://www.rahul.net/aahz/
> Hugs and backrubs -- I break Rule 6
> 
> "Characters exist to suffer, you know.  An author needs a little sadism
> in her makeup."  --Brenda Clough

-- 
Greg Copeland, Principal Consultant
Copeland Computer Consulting
--------------------------------------------------
PGP/GPG Key at http://www.keyserver.net
DE5E 6F1D 0B51 6758 A5D7  7DFE D785 A386 BD11 4FCD
--------------------------------------------------