[issue42509] Recursive calls crash interpreter when checking exceptions

2020-11-30 Thread Mark Shannon
Mark Shannon added the comment: Duplicate of 42500 -- nosy: +Mark.Shannon resolution: -> duplicate stage: -> resolved status: open -> closed ___ Python tracker ___

[issue42509] Recursive calls crash interpreter when checking exceptions

2020-11-30 Thread Dennis Sweeney
Dennis Sweeney added the comment: sys.getrecursionlimit() returns whatever was passed to the most recent call of sys.setrecursionlimit(...), with some system default (here 1000). Catching a RecursionError might be fine sometimes, but the issue is that Program 1 catches a RecursionError *and

[issue42509] Recursive calls crash interpreter when checking exceptions

2020-11-30 Thread Xinmeng Xia
Xinmeng Xia added the comment: But program like following program 3 will not cause any core dump, RecursionError is also being caught in this Recursion. program 3 def rec(): try: rec() except: pass rec() Beside,I use sys.setrecursionlimit(80),

[issue42509] Recursive calls crash interpreter when checking exceptions

2020-11-30 Thread Ronald Oussoren
Ronald Oussoren added the comment: See also #42500 -- nosy: +ronaldoussoren ___ Python tracker ___ ___ Python-bugs-list mailing

[issue42509] Recursive calls crash interpreter when checking exceptions

2020-11-29 Thread Dennis Sweeney
Dennis Sweeney added the comment: This might be the expected behavior. See https://bugs.python.org/issue25222 If you already caught a RecursionError and you keep recursing anyway, once you go 50 levels beyond sys.getrecursionlimit(), the interpreter crashes regardless of what is `except`ed.

[issue42509] Recursive calls crash interpreter when checking exceptions

2020-11-29 Thread Xinmeng Xia
New submission from Xinmeng Xia : The following program 1 can crash in Python 3. We have reproduce it in the Python version 3.5, 3.6, 3.7, 3.8, 3.9, 3.10. This bug seems to be similar to issue 36272, however, the tracking system shows issue 36272 has been fixed and the program 2, which