Antoine Pitrou <[EMAIL PROTECTED]> added the comment:
Selon STINNER Victor <[EMAIL PROTECTED]>:
>
> > How can tstate->exc_value become NULL at that point? [error.c:86]
> > Could you investigate?
>
> PyEval_CallObject(exception, args) may calls PyErr_SetObject(). Since
> the same thread state is the same, tstate->exc_value also changes
> during this call.
Hmm, indeed.
However, I don't see why your Python code triggers that. Does instantiating the
ProcError object somehow fail, and for what reason? Or did you witness it in
other circumstances?
As for the original problem ("tstate->exc_traceback points to a zombi object")
it would be nice to have a small snippet of Python code to reproduce it. Is it
possible for you to do that?
_______________________________________
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue3611>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
