Message71739
Victor, your patch addresses the symptom of the problem, not the cause.
The cause is that in some cases, the exception context chain is lost. Of
course what could be a minor annoyance becomes dramatic when this
precisely happens in code that makes use of this context.
IMO, PyErr_SetObject should not restore the previous exc_* members; it's
not its job to correct others' mistakes.
I join a patch that only protects it from crashing in this case: it just
saves exc_value in a local variable.
The bug shown by lostcontext2.py is still unresolved, but at least it
won't crash the interpreter. |
|
Date |
User |
Action |
Args |
2008-08-22 10:08:56 | amaury.forgeotdarc | set | recipients:
+ amaury.forgeotdarc, pitrou, vstinner, benjamin.peterson |
2008-08-22 10:08:56 | amaury.forgeotdarc | set | messageid: <1219399736.03.0.207425184128.issue3611@psf.upfronthosting.co.za> |
2008-08-22 10:07:55 | amaury.forgeotdarc | link | issue3611 messages |
2008-08-22 10:07:54 | amaury.forgeotdarc | create | |
|