[Python-bugs-list] Re: [Bug #111403] 1.6b1 dumps core dereferencing a NULL tstate

[Jeremy Hylton]

  MR> Date: 2000-Sep-15 12:45 By: romberg

  MR> Comment:
  MR>   Yes.  I've tried things with both 1.6 (final) and 2.0b1 on
  MR>   RH6.2.  For
  MR> both versions of python, things work fine as long as
  MR> --without-thread is used to build python.  The HPUX issue is not
  MR> really important to me.  I only tried building things on it to
  MR> use Purify (to verify that there were no memory related problems
  MR> with the code).  I understand that the threads on HPUX-10.20 are
  MR> a real mess.  I don't really care much about getting python
  MR> threads working on HPUX.

  MR>   But I would like to use them on linux (so we can use things
  MR>   like Zope).
  MR> So, at this time the symptoms are still that things work fine
  MR> using python-1.5.2 (with and without threads).  But, die when
  MR> threads are enabled.  None of our code is using any kind of
  MR> threads (pthreads or python threads).  I'm not using any part of
  MR> the python C API which deals with threads (maybe I should now be
  MR> doing so?).  So, the only thing I can think of is that there is
  MR> now some kind of thread thing going on in _tkinter which was not
  MR> in python-1.5.2.  Since the core dump seems to happen after our
  MR> C++ code is woken up from a Tcl filehandler and then calls back
  MR> into python.  This is just a guess :).

Ok.  There is a real bug to report here, but this particular bug
report -- about threads and HPUX -- is not what the real problem is.

Can you open a new bug report that explains what the real problem is?
It seems that you have some application that embeds Python and uses
Tcl that is crashing when Python 2.0b1 is compiled with threads.  Can
you fill in enough details to let someone else help?

Thanks,
Jeremy