classification
Title: Segmentation fault in running ast.parse() with large expression size.
Type: crash Stage: resolved
Components: Interpreter Core Versions: Python 3.10, Python 3.9, Python 3.8, Python 3.7, Python 3.6
process
Status: closed Resolution: duplicate
Dependencies: Superseder: Segmentation fault in running ast.literal_eval() with large expression size.
View: 42712
Assigned To: Nosy List: serhiy.storchaka, stestagg, xxm
Priority: normal Keywords:

Created on 2020-12-22 10:21 by xxm, last changed 2020-12-26 01:40 by terry.reedy. This issue is now closed.

Messages (3)
msg383581 - (view) Author: Xinmeng Xia (xxm) Date: 2020-12-22 10:21
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. The primary difference between these two examples lay on the value of "n".



Example 1:
=========================================
import ast
mylist = []
n = 100000
print(ast.parse("mylist"+"+mylist"*n))
==========================================

The actual output: AST nodes on Python 3.5-3.10 (as expected)
# <_ast.Module object at 0x7f78d7b672e8>
 


Example 2:
===================================
import ast
mylist = []
n = 1000000
print(ast.parse("mylist"+"+mylist"*n))
# <_ast.Module object at 0x7f78d7b672e8>
===================================

The actual output: segmentation fault on Python 3.5 - 3.10 (not as expected)




My system information:

>> python3.10 -V
Python 3.10.0a2

>> python3.9 -V
Python 3.9.0rc1

>> python3.8 -V
Python 3.8.0

>> python3.7 -V
Python 3.7.3

>> python3.6 -V
Python 3.6.12

>> uname -v
#73~16.04.1-Ubuntu
msg383603 - (view) Author: Steve Stagg (stestagg) Date: 2020-12-22 19:18
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 the new recursion error is probably expected and acceptable.
msg383611 - (view) Author: Steve Stagg (stestagg) Date: 2020-12-22 20:07
fyi, Issue42712, Issue42712, Issue42714, Issue42715, Issue42716 all seem to be variants of the same underlying problem
History
Date User Action Args
2020-12-26 01:40:38terry.reedysetstatus: open -> closed
superseder: Segmentation fault in running ast.literal_eval() with large expression size.
resolution: duplicate
stage: resolved
2020-12-22 20:07:19stestaggsetmessages: + msg383611
2020-12-22 19:18:39stestaggsetnosy: + stestagg, serhiy.storchaka
messages: + msg383603
2020-12-22 10:21:33xxmcreate