[issue42500] crash with unbounded recursion in except statement

Change by Łukasz Langa : -- superseder: -> Cannot Recover From StackOverflow in 3.9 Tests ___ Python tracker ___ ___ Python-bugs-lis

[issue42500] crash with unbounded recursion in except statement

Łukasz Langa added the comment: New changeset c7b0feca25fc68ec3e0884b82e5f45a4da011e8e by Gregory P. Smith in branch '3.9': [3.9] bpo-43710: Rollback the 3.9 bpo-42500 fix, it broke the ABI in 3.9.3 (#25179) https://github.com/python/cpython/commit/c7b0feca25fc68ec3e0884b82e5f45a4da011e8e -

[issue42500] crash with unbounded recursion in except statement

Change by Gregory P. Smith : -- nosy: +gregory.p.smith nosy_count: 7.0 -> 8.0 pull_requests: +23921 pull_request: https://github.com/python/cpython/pull/25179 ___ Python tracker __

[issue42500] crash with unbounded recursion in except statement

Change by Mark Shannon : -- pull_requests: +23290 pull_request: https://github.com/python/cpython/pull/24501 ___ Python tracker ___

[issue42500] crash with unbounded recursion in except statement

Change by Mark Shannon : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___

[issue42500] crash with unbounded recursion in except statement

Mark Shannon added the comment: New changeset 4e7a69bdb63a104587759d7784124492dcdd496e by Mark Shannon in branch 'master': bpo-42500: Fix recursion in or after except (GH-23568) https://github.com/python/cpython/commit/4e7a69bdb63a104587759d7784124492dcdd496e -- ___

[issue42500] crash with unbounded recursion in except statement

Change by Mark Shannon : -- keywords: +patch pull_requests: +22449 stage: -> patch review pull_request: https://github.com/python/cpython/pull/23568 ___ Python tracker ___ ___

[issue42500] crash with unbounded recursion in except statement

Mark Shannon added the comment: Ronald's test case also causes a Fatal Error on master. 2.7.18 produces the expected "RuntimeError: maximum recursion depth exceeded" -- assignee: -> Mark.Shannon ___ Python tracker

[issue42500] crash with unbounded recursion in except statement

Ronald Oussoren added the comment: See also #42509 -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:

[issue42500] crash with unbounded recursion in except statement

Ronald Oussoren added the comment: As mentioned earlier I can reproduce this without calling os.fstat (python 3.9.1rc, macOS 10.15): # --- def status(): try: 1/0 except status(): pass status() # The crash happens both with the default recursion limit as well with a

[issue42500] crash with unbounded recursion in except statement

Eric V. Smith added the comment: Note that changing the os.fstat line to just "raise OSError()" no longer causes the "Fatal Python error", but rather gives the expected recursion exception. Here's a shorter version that causes the fatal error in Windows native 3.9, cygwin 3.8.3, and Fedora L

[issue42500] crash with unbounded recursion in except statement

Eric V. Smith added the comment: Here's the smallest reproducer I could come up with. It fails on Windows with 3.9 native(compiled locally) (Fatal Python error: _Py_CheckRecursiveCall: Cannot recover from stack overflow), works (raises RecursionError) with cygwin 3.8.3. import os def statu

[issue42500] crash with unbounded recursion in except statement

Change by Serhiy Storchaka : -- nosy: +Mark.Shannon, serhiy.storchaka ___ Python tracker ___ ___ Python-bugs-list mailing list Unsub

[issue42500] crash with unbounded recursion in except statement

Ronald Oussoren added the comment: The value of the recursion limit is not relevant here, I get the same crash when I set the recursion limit to 100 (in my reproducer scriptlet). There might be a missing recursion level check in the exception handling machinery though, self-recursion in an e

[issue42500] crash with unbounded recursion in except statement

Vedran Čačić added the comment: Recursion limit is probably set too high, but nonetheless, the program is nonsensical, the line 39 especially. The reason for difference in behavior is that RecursionError is caught by blank except in the earlier Pythons, while it crashes the stack in later one

[issue42500] crash with unbounded recursion in except statement

Change by Ronald Oussoren : -- title: status() crashes on Python3.9 and 3.10 -> crash with unbounded recursion in except statement ___ Python tracker ___ _