[New-bugs-announce] [issue10933] Tracing disabled when a recursion error is triggered (even if properly handled)
report at bugs.python.org
Tue Jan 18 13:31:12 CET 2011
New submission from Fabio Zadrozny <fabioz at users.sourceforge.net>:
It seems that tracing in the interpreter is lost after some recursion error is triggered (even if it's properly handled).
This breaks any debugger working after any recursion error is triggered (which suppose shouldn't happen).
The attached test case shows the problem in action.
Tested the problem with Python 2.6.5 and 3.1.3
components: Interpreter Core
title: Tracing disabled when a recursion error is triggered (even if properly handled)
versions: Python 2.6, Python 3.1
Added file: http://bugs.python.org/file20436/recursion_error_disables_tracing.py
Python tracker <report at bugs.python.org>
More information about the New-bugs-announce