On Wed, 2005-13-04 at 01:17 -0300, Johan Dahlin wrote: > Brian wrote: > > >I have a problem in that another python program (not under our > >development) we import is not thread friendly. The problem I have is > >that mostly it is imported and used from the base thread, but there are > >several areas of code that need to run from a thread so as to not tie up > >the mainloop and general gui operations. The result is intermittent > >segfaults/ lately it does: > > > >Fatal Python error: PyThreadState_Get: no current thread > >Killed > > > > try setting the environment variable PYGTK_USE_GIL_STATE_API to true > before calling gobject.threads_init() > > Johan
It locks up at another thread that produces the data needed for a different view. It is showing that different view and then activating the problem thread that seems to cause the intermittent segfaults/PyThreadState_Get more often. -- Brian <[EMAIL PROTECTED]> _______________________________________________ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
