[issue42716] Segmentation fault in running ast.parse() with large expression size.

Change by Terry J. Reedy : -- resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> Segmentation fault in running ast.literal_eval() with large expression size. ___ Python tracker

[issue42716] Segmentation fault in running ast.parse() with large expression size.

Steve Stagg added the comment: fyi, Issue42712, Issue42712, Issue42714, Issue42715, Issue42716 all seem to be variants of the same underlying problem -- ___ Python tracker

[issue42716] Segmentation fault in running ast.parse() with large expression size.

Steve Stagg added the comment: PR: https://github.com/python/cpython/pull/23744 stops this from segfaulting. It does however raise a RecursionError: RecursionError: maximum recursion depth exceeded during compilation As per https://bugs.python.org/issue42609#msg382910, Serhiy implies that

[issue42716] Segmentation fault in running ast.parse() with large expression size.

New submission from Xinmeng Xia : Calling function ast.parse() with large size can cause a segmentation fault in Python 3.5 -3.10. Please check the following two examples. The example 1 works as expected, while the second one triggers segmentation fault on Python 3.5,3.6,3.7,3.8,3.9,3.10.