This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author steve.dower
Recipients aleReimondo, paul.moore, steve.dower, tim.golden, zach.ware
Date 2021-08-13.21:38:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1628890731.51.0.635487940262.issue44906@roundup.psfhosted.org>
In-reply-to
Content
I get stack overflows all the way back to 3.7, so it's probably not anything new. But our stack overflow detection is clearly not going to catch this case. It's really only set up for a direct call within Python code, but this is going through many more steps.

Best thing you can do as a user is run it with "python -X faulthandler ..." to see the error. Perhaps we can handle the stack overflow ourselves and print a message suggesting that option, but unfortunately this problem doesn't have a generic solution :( The assumption is that you have a known recursion limit for your application, and as a scripting engine, we don't. Decoupling from the C stack is the best hope.
History
Date User Action Args
2021-08-13 21:38:51steve.dowersetrecipients: + steve.dower, paul.moore, tim.golden, zach.ware, aleReimondo
2021-08-13 21:38:51steve.dowersetmessageid: <1628890731.51.0.635487940262.issue44906@roundup.psfhosted.org>
2021-08-13 21:38:51steve.dowerlinkissue44906 messages
2021-08-13 21:38:51steve.dowercreate