homepage

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 nedbat
Recipients nedbat
Date 2009年06月28日.22:43:20
SpamBayes Score 9.756112e-05
Marked as misclassified No
Message-id <1246229003.36.0.107970043042.issue6359@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2009年06月28日 22:43:23nedbatsetrecipients: + nedbat
2009年06月28日 22:43:23nedbatsetmessageid: <1246229003.36.0.107970043042.issue6359@psf.upfronthosting.co.za>
2009年06月28日 22:43:21nedbatlinkissue6359 messages
2009年06月28日 22:43:21nedbatcreate

AltStyle によって変換されたページ (->オリジナル) /