Python + threads + wxWindows = segfault, help!

Greg Copeland gtcopeland at
Sat Jun 2 21:42:44 CEST 2001

Thanks! My forehead won't be so sore now!  BTW, if you need any help
working on it, or you just want someone to help test, please let me
know.  I'll be glad to help.  Thanks again for the response!!!


P.S.  This application does not use wxPostEvent(), so I'm guessing the
problem doesn't lie there.

"Robin Dunn" <robin at> writes:

> > 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.
> This is a known bug that has been around for some time.  It only happens on
> SMP hardware, which I don't have yet, so there have been a couple blind
> attempts at a fix that have failed.
> My new SMP motherboard and processors and etc. arrive next week, so
> hopefully soon I'll be able to better understand the problem and then come
> up with a solution.  (Just don't tell my wife that all this new hardware
> ($$$) was only bought to squash a bug in free software...)
> NT and Win2k users can work around the problem by telling the OS to keep the
> process on just one processor:
>     import win32api, win32process
>     cp = win32api.GetCurrentProcess()
>     win32process.SetProcessAffinityMask(cp, 1)
> You can keep track of the bug here:
> 9863
> --
> Robin Dunn
> Software Craftsman
> robin at       Java give you jitters?
>      Relax with wxPython!

Greg Copeland, Principal Consultant
Copeland Computer Consulting
PGP/GPG Key at
DE5E 6F1D 0B51 6758 A5D7  7DFE D785 A386 BD11 4FCD

More information about the Python-list mailing list