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

[Gordon P. Hemsley]

Change by Gordon P. Hemsley :


--
nosy: +gphemsley

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Mark Lawrence]

Change by Mark Lawrence :


--
nosy:  -BreamoreBoy

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Fabio Zadrozny]

Fabio Zadrozny added the comment:

Well, I'd say that if tracing is enabled and is disabled automatically by 
Python (thus breaking a working debugger which would usually be used to 
diagnose the error), I'd at least consider issuing some warning to stderr... 
(probably warnings.warn cannot be used directly as the stack is at its max 
depth, but a choice could be raising the max depth, using warnings.warn and 
then restoring the max depth value in a try..finally -- or at least printing 
something to stderr regardless of warnings.warn).

I.e.: as this is a rare situation and should only happen when you're debugging, 
I think printing something to stderr regarding that is definitely worth it 
regardless of chained exceptions (on many cases I had to help users instrument 
a simple tracer just to detect where it was disabled -- yes, on some of those 
they were catching all exceptions on some block -- so, program which worked 
with the recursion stopped having a working debugger).

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10933
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[R. David Murray]

R. David Murray added the comment:

We also discussed whether or not it would be worth indicating in the exception 
that tracing has been disabled.  I believe that implementing this would be 
aided by resolution of issue 23188.  Doing a chained exception for this would 
also make it clearer that the exception happened inside the trace function.

It is not clear that it is sensible to allow tracing to continue if the trace 
function raises an error, since that pretty much leaves the tracer or debugger 
or what have you in an undefined state.  It is also not clear that there is any 
reasonable way to try to avoid a recursion error in the trace function when we 
are near the recursion limit in the underlying code, since the stack depth of 
the trace function is pretty much arbitrary.

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10933
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Peter McCormick]

Peter McCormick added the comment:

Removed unrelated doc changes.

--
Added file: http://bugs.python.org/file38909/issue_10933-2.patch

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10933
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[James Powell]

James Powell added the comment:

We investigated this issue with pdmccormick  r.david.murray.

The behaviour appears to be intentional. If the trace function raises an 
Exception, system tracing is disabled entirely.

See attached documentation patch to clarify this.

--
keywords: +patch
Added file: http://bugs.python.org/file38908/issue_10933.patch

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10933
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[James Powell]

Changes by James Powell ja...@dontusethiscode.com:


--
nosy: +james, r.david.murray

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10933
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Peter McCormick]

Changes by Peter McCormick pe...@pdmccormick.com:


--
nosy: +pdmccormick

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10933
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Mark Lawrence]

Mark Lawrence added the comment:

Can we have a response to this please.

--
nosy: +BreamoreBoy
versions: +Python 2.7, Python 3.4, Python 3.5 -Python 2.6, Python 3.1

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10933
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Fabio Zadrozny]

New submission from Fabio Zadrozny fab...@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 rep...@bugs.python.org
http://bugs.python.org/issue10933
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com