[issue42712] Segmentation fault in running ast.literal_eval() with large expression size.

Change by Irit Katriel : -- resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> Eval with too high string multiplication crashes newer Python versions ___ Python tracker

[issue42712] Segmentation fault in running ast.literal_eval() with large expression size.

Raymond Hettinger added the comment: I think we really need a customer parser for ast.literal_eval(), one that doesn't have the same constraints and that can be counted on for safe evaluation of untrusted input. -- nosy: +rhettinger ___ Python

[issue42712] Segmentation fault in running ast.literal_eval() with large expression size.

Terry J. Reedy added the comment: I closed the following by Xinmeng as duplicates of this: #42713 eval(...) #42714 compile(...) #42715 exec(...) #42716 ast.parse(...) This is probably a duplicate of #42609, and should likely be closed also. -- nosy: +terry.reedy

[issue42712] Segmentation fault in running ast.literal_eval() with large expression size.

Steve Stagg added the comment: Confirmed fixed by https://github.com/python/cpython/pull/23744: Traceback (most recent call last): File "/home/sstagg/tmp/fuzztest/cpython/../test.py", line 4, in print(ast.literal_eval("mylist"+"+mylist"*n)) File

[issue42712] Segmentation fault in running ast.literal_eval() with large expression size.

Steve Stagg added the comment: Likely duplicate of Issue42609, Probably fixed by bpo-42609 -- nosy: +stestagg ___ Python tracker ___

[issue42712] Segmentation fault in running ast.literal_eval() with large expression size.

New submission from Xinmeng Xia : Calling function ast.literal_eval() 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