Message89798
Pyexpat.c calls the tracing function explicitly (not sure why). When it
intercepts an exception, it calls the function with PyTrace_EXCEPTION,
but then leaves the scope without calling PyTrace_RETURN. This is
incorrect. There should always be a PyTrace_RETURN for every PyTrace_CALL.
I've attached domshow.py to demonstrate the problem.
Running it produces many lines of output, including:
line expatbuilder.py 222
line expatbuilder.py 223
call pyexpat.c 905
call expatbuilder.py 892
line expatbuilder.py 894
line expatbuilder.py 900
exception expatbuilder.py 900
return expatbuilder.py 900
exception pyexpat.c 905
exception expatbuilder.py 223
line expatbuilder.py 225
line expatbuilder.py 226
The exception at line 905 in pyexpat.c should be followed with a return
from line 905 in pyexpat.c, but is not. After that exception, the
nesting is off by one because the Calls and Returns don't match. |
|
Date |
User |
Action |
Args |
2009-06-28 22:43:23 | nedbat | set | recipients:
+ nedbat |
2009-06-28 22:43:23 | nedbat | set | messageid: <1246229003.36.0.107970043042.issue6359@psf.upfronthosting.co.za> |
2009-06-28 22:43:21 | nedbat | link | issue6359 messages |
2009-06-28 22:43:21 | nedbat | create | |
|