Message80759
I think I have an explanation:
When a python exception is raised, the current call stack is stored in
the exception state (tstate->curexc_traceback). This includes all the
living frame objects, with all their local variables.
This explains why frame_dealloc is not called at this time, and why the
"self" object has its refcount increased.
PyErr_Clear() releases everything.
PyErr_Print() does clear tstate->curexc_traceback, but only to copy the
value into sys.last_traceback; So the frame object is still alive.
I suggest you to use PyErr_PrintEx(0), which will print and clear the
error, but not store the exception info into the sys.last_* variables.
[PyErr_Print() simply calls PyErr_PrintEx(1); No, it's not yet documented] |
|
Date |
User |
Action |
Args |
2009-01-29 12:06:33 | amaury.forgeotdarc | set | recipients:
+ amaury.forgeotdarc, exe |
2009-01-29 12:06:33 | amaury.forgeotdarc | set | messageid: <1233230793.03.0.302257723482.issue5096@psf.upfronthosting.co.za> |
2009-01-29 12:06:30 | amaury.forgeotdarc | link | issue5096 messages |
2009-01-29 12:06:30 | amaury.forgeotdarc | create | |
|