[New-bugs-announce] [issue10933] Tracing disabled when a recursion error is triggered (even if properly handled)

[Fabio Zadrozny]

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
files: recursion_error_disables_tracing.py
messages: 126460
nosy: fabioz
priority: normal
severity: normal
status: open
title: Tracing disabled when a recursion error is triggered (even if properly handled)
type: behavior
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>
<http://bugs.python.org/issue10933>
_______________________________________