[issue28179] Segfault in test_recursionlimit_fatalerror

2021-02-17 Thread Berker Peksag
Berker Peksag added the comment: Yes, this indeed seems to be fixed by issue 42500 and can be closed now. Nice detective work, thank you! -- stage: needs patch -> resolved status: pending -> closed ___ Python tracker

[issue28179] Segfault in test_recursionlimit_fatalerror

2021-02-17 Thread Irit Katriel
Irit Katriel added the comment: I'm not seeing this crash on master. I believe is was fixed under issue42500, which add this case as a unit test: see recurse_in_body_and_except in

[issue28179] Segfault in test_recursionlimit_fatalerror

2016-10-10 Thread Ned Deily
Ned Deily added the comment: Since this is also reproducible on some 3.5.2 platforms, I don't think it qualifies as a release blocker for 3.6.0. But it still should be addressed. -- priority: release blocker -> high ___ Python tracker

[issue28179] Segfault in test_recursionlimit_fatalerror

2016-09-17 Thread Terry J. Reedy
Terry J. Reedy added the comment: And the test passes on Windows on both versions. -- ___ Python tracker ___

[issue28179] Segfault in test_recursionlimit_fatalerror

2016-09-17 Thread Terry J. Reedy
Terry J. Reedy added the comment: I also got the same result on 3.5 as 3.6. -- ___ Python tracker ___ ___

[issue28179] Segfault in test_recursionlimit_fatalerror

2016-09-17 Thread Berker Peksag
Berker Peksag added the comment: What do you mean by crash? I think the purpose of the test is to crash the interpreter: def test_recursionlimit_fatalerror(self): # A fatal error occurs if a second recursion limit is hit when recovering # from a first one. ...

[issue28179] Segfault in test_recursionlimit_fatalerror

2016-09-17 Thread Xiang Zhang
Xiang Zhang added the comment: This snippet also crashes in Py3.5 -- nosy: +larry, xiang.zhang versions: +Python 3.5 ___ Python tracker ___

[issue28179] Segfault in test_recursionlimit_fatalerror

2016-09-16 Thread Serhiy Storchaka
Changes by Serhiy Storchaka : -- nosy: +ned.deily priority: normal -> release blocker ___ Python tracker ___

[issue28179] Segfault in test_recursionlimit_fatalerror

2016-09-16 Thread Terry J. Reedy
Terry J. Reedy added the comment: Running with fresh build from IDLE in a subprocess on Win10, with 15 instead of 10, I quickly get a fatal Python error and the Windows box equivalent to a segfault. -- nosy: +terry.reedy ___ Python tracker

[issue28179] Segfault in test_recursionlimit_fatalerror

2016-09-16 Thread Berker Peksag
Changes by Berker Peksag : Added file: http://bugs.python.org/file44688/full_output.txt ___ Python tracker ___

[issue28179] Segfault in test_recursionlimit_fatalerror

2016-09-16 Thread Berker Peksag
New submission from Berker Peksag: This is a follow-up from msg275748 in issue 27213 (Rework CALL_FUNCTION* opcodes). I believe the test_runpy failure I mentioned there is also the same error, but this one can be reproduced easily. test_recursionlimit_fatalerror in SysModuleTest