Stefan Nordhausen <stefan.nordhau...@solarisbank.de> added the comment:
The fix for https://bugs.python.org/issue31113 also fixed this issue.
--
resolution: -> duplicate
stage: -> resolved
status: open -> closed
___
Pyth
Change by Stefan Nordhausen <stefan.nordhau...@solarisbank.de>:
--
nosy: +snordhausen
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python
Stefan Nordhausen <stefan.nordhau...@solarisbank.de> added the comment:
I tried out PR 3015 of Serhiy and this fixes the segfaults. So it seems to be a
duplicate.
As for backporting the fix: Is this a 'reliable' segfault (i.e. it always
segfaults when the limit is exceeded) or
New submission from Stefan Nordhausen <stefan.nordhau...@solarisbank.de>:
The following code reproducibly segfaults in version 2.7.13, 3.6.3 and the
current git master (3.7.0a3+):
code = "42 if True else 43\n" * 20
compile(code, "foobar", "exec")
Thi
