[issue30734] 200000 indexes crashes eval and python (without eval)

Nick Coghlan added the comment: We have quite a few of them: https://github.com/python/cpython/tree/master/Lib/test/crashers Python 2.7 is ancient, so our tolerance for intrusive interpreter level fixes to address rare problems that are easy to avoid at the development level is pretty low.

[issue30734] 200000 indexes crashes eval and python (without eval)

George Shuklin added the comment: Unfixed crash of code interpreter? This is sad. -- ___ Python tracker ___

[issue30734] 200000 indexes crashes eval and python (without eval)

Serhiy Storchaka added the comment: Which is a duplicate of issue5765 fixed for Python 3.3+. It was decided to not fix issue5765 for 2.7. -- nosy: +serhiy.storchaka resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> stack overflow evaluating eval("()"

[issue30734] 200000 indexes crashes eval and python (without eval)

Mark Dickinson added the comment: Looks like a duplicate of http://bugs.python.org/issue7985 -- nosy: +mark.dickinson ___ Python tracker ___

[issue30734] 200000 indexes crashes eval and python (without eval)

Terry J. Reedy added the comment: To be clear, as the title and version suggest, the bug is the 2.7 segfault versus the 3.x exception during compile. It is normal for the compiler to have limits and to exit when they are exceeded. I have no idea if the 3.x code can be backported. I added

[issue30734] 200000 indexes crashes eval and python (without eval)

New submission from George Shuklin: If there is too many indexes python crashes: a[0][0][0][0] segfault at 7ffd25fe6ff8 ip 564528c8cfe6 sp 7ffd25fe7000 error 6 in python2.7[564528b6a000+324000] code to generate code: >>> i="[0]"*20 >>>