[issue35534] SIGSEGV in stackdepth_walk

Irit Katriel added the comment: Python 2-only issue. -- nosy: +iritkatriel resolution: -> out of date stage: -> resolved status: open -> closed ___ Python tracker ___ __

[issue35534] SIGSEGV in stackdepth_walk

anthony shaw added the comment: stackdepth_walk no longer exists in Python 3, this is a 2.7 specific issue. opcode_stack_effect in compile.c will have the expected stack effect. If there is a mismatch between the Opcodes compiled with the distribution and the ones in the compile.c opcode_sta

[issue35534] SIGSEGV in stackdepth_walk

Marcin Gozdalik added the comment: #0 0x004f4af3 in stackdepth_walk (maxdepth=5, depth=3, b=, c=) at ../Python/compile.c:3436 #1 stackdepth_walk (maxdepth=, depth=0, b=, c=0x7fff4f5b84f0) at ../Python/compile.c:3456 #2 stackdepth (c=0x7fff4f5b84f0) at ../Python/compile.c:3486 #3 ma

[issue35534] SIGSEGV in stackdepth_walk

New submission from Marcin Gozdalik : When running /usr/bin/python /usr/bin/pip install --upgrade "pip < 10" the interpreter crashed in stackdepth_walk. I've seen this crash multiple times, especially in our custom-compiled CPythons. Here it's reproduced with stock Ubuntu Xenial Python. It l