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 amaury.forgeotdarc
Recipients amaury.forgeotdarc, pitrou, vstinner
Date 2008-08-20.19:50:54
SpamBayes Score 2.2323863e-07
Marked as misclassified No
Message-id <1219261856.15.0.41554618228.issue3611@psf.upfronthosting.co.za>
In-reply-to
Content
The problem comes when PyErr_SetObject triggers garbage collection which
runs python code (finalizers...).

I could reproduce the crash several times, and each time garbage
collection was triggered by the normalization of the exception (the call
to PyEval_CallObject(exception, args)).

An obvious fix is to save exc_value near the "/* Implicit exception
chaining */" comment.

However, I fear that there are other places where exc_value is reset,
and "exception chaining" may break in subtle ways.
History
Date User Action Args
2008-08-20 19:50:56amaury.forgeotdarcsetrecipients: + amaury.forgeotdarc, pitrou, vstinner
2008-08-20 19:50:56amaury.forgeotdarcsetmessageid: <1219261856.15.0.41554618228.issue3611@psf.upfronthosting.co.za>
2008-08-20 19:50:55amaury.forgeotdarclinkissue3611 messages
2008-08-20 19:50:54amaury.forgeotdarccreate