Ned Deily <n...@python.org> added the comment:
Thank you for the report. The issue of the interpreter not being able to gracefully handle a stack overflow error is an old one: see, for example Issue18075 or Issue35542. So far, no one has proposed a solution and, as can be seen in Issue18075, workarounds someimes produce unexpected side-effects that can be more problematic than the stack overflow segfault. I'm going to close this as a duplicate of Issue18075. If anyone has further suggestions for solutions, please continue the discussion there. ---------- nosy: +ned.deily resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> Infinite recursion tests triggering a segfault _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue37365> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
