[issue24828] Segfault when using store-context AST node in a load context

Change by Serhiy Storchaka : -- resolution: -> out of date stage: -> resolved status: open -> closed ___ Python tracker ___ ___

[issue24828] Segfault when using store-context AST node in a load context

Xavier Morel added the comment: Should I close this since I believe 2.7 is not supported anymore? -- ___ Python tracker ___ ___

[issue24828] Segfault when using store-context AST node in a load context

Change by Serhiy Storchaka : -- versions: -Python 3.2 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue24828] Segfault when using store-context AST node in a load context

Karthikeyan Singaravelan added the comment: Reproducible on latest 2.7 branch as well. Stack trace as below : Program received signal SIGSEGV, Segmentation fault. dict_set_item_by_hash_or_entry ( op={'code': , 'ast': , '__builtins__': , '__file__': '../backups/bpo24828.py', 'm': ,

[issue24828] Segfault when using store-context AST node in a load context

Karthikeyan Singaravelan added the comment: Thanks for the script. The crash is still reproducible as of now with at least python 2.7.14 . I need to check on the latest 2.7 branch yet. On python 3 it produces an error as below : Traceback (most recent call last): File

[issue24828] Segfault when using store-context AST node in a load context

New submission from Xavier Morel: It looks to be fixed in 3.3 and up, but in Python 2.7 import ast m = ast.Module(body=[ ast.Expr(value=ast.Name(id='foo', ctx=ast.Store())) ]) ast.fix_missing_locations(m) code = compile(m, '', mode='exec') eval(code) will