Message 71551 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	pitrou
Recipients	pitrou, vstinner
Date	2008-08-20.15:24:22
SpamBayes Score	0.00027821554
Marked as misclassified	No
Message-id	<1219245886.48ac373e03174@imp.free.fr>
In-reply-to	<1219244300.3.0.371494872668.issue3611@psf.upfronthosting.co.za>

Content
Selon STINNER Victor <report@bugs.python.org>: > > > 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?

Selon STINNER Victor <report@bugs.python.org>:
>
> > 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?

History
Date	User	Action	Args
2008-08-20 15:24:25	pitrou	set	recipients: + pitrou, vstinner
2008-08-20 15:24:24	pitrou	link	issue3611 messages
2008-08-20 15:24:22	pitrou	create