[issue13644] Python 3 crashes (segfaults) with this code.

Roger Serwy added the comment: With Python 2, I can inspect the error to see where it occurred using traceback. With Python 3, I'd need to use gdb. -- nosy: +serwy ___ Python tracker _

[issue13644] Python 3 crashes (segfaults) with this code.

Benjamin Peterson added the comment: There is no place for it to raise a RuntimeError which will continue to propogate! -- ___ Python tracker ___ __

[issue13644] Python 3 crashes (segfaults) with this code.

maniram maniram added the comment: Well, I expect Python 3 to raise RuntimeError about recursion not to segfault. -- ___ Python tracker ___ _

[issue13644] Python 3 crashes (segfaults) with this code.

Benjamin Peterson added the comment: The behavior of Python 2 is not anymore correct than that of Python 3. -- ___ Python tracker ___ ___

[issue13644] Python 3 crashes (segfaults) with this code.

maniram maniram added the comment: Oops, to reproduce this bug after running the code run "recurse()". -- ___ Python tracker ___ ___

[issue13644] Python 3 crashes (segfaults) with this code.

maniram maniram added the comment: But Python 2 doesn't crash after running the code. -- ___ Python tracker ___ ___ Python-bugs-list

[issue13644] Python 3 crashes (segfaults) with this code.

Benjamin Peterson added the comment: Python isn't crashing; it's bailing out of an impossible situation. It's not clear what the correct behavior is, since you're basically preventing Python from aborting the recursive behavior. -- nosy: +benjamin.peterson ___

[issue13644] Python 3 crashes (segfaults) with this code.

Changes by maniram maniram : -- title: Python 3 crashes with this code. -> Python 3 crashes (segfaults) with this code. ___ Python tracker ___ __