STINNER Victor <[EMAIL PROTECTED]> added the comment: It's now known that PyErr_SetObject() have to be re-entrant because of the garbage collector interaction. As I wrote in my comments, tstate may be changed during PyEval_CallObject() call. The problem is to known which values have to be protected during PyErr_SetObject() re-entrant call... I tried to save/restore tstate->exc_value if it's value changes, but I'm not sure that it's enough.
Added file: http://bugs.python.org/file11201/pyerr_setobject_reentrant.patch _______________________________________ 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
