[issue23012] RuntimeError: settrace/setprofile function gets lost

Batuhan added the comment: I try to track down this. sys_settrace calls PyEval_SetTrace with trace_trampoline and the function given to it. The trace_trampoline is important because it checks the result and if result is NULL (for example like f() recursion in your code) it sets c_tracefunc

[issue23012] RuntimeError: settrace/setprofile function gets lost

Change by Batuhan : -- nosy: +BTaskaya ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.or

[issue23012] RuntimeError: settrace/setprofile function gets lost

Change by Batuhan : -- versions: +Python 3.7, Python 3.8 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http

[issue23012] RuntimeError: settrace/setprofile function gets lost

Change by Gordon P. Hemsley : -- nosy: +gphemsley ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mai

[issue23012] RuntimeError: settrace/setprofile function gets lost

Changes by STINNER Victor : -- nosy: +haypo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python

[issue23012] RuntimeError: settrace/setprofile function gets lost

New submission from Armin Rigo: It's not possible to write a settrace() or setprofile() function that remains active if we're about to run out of stack. If we are, we get a RuntimeError when the function is called. The RuntimeError is normally propagated, but in case it is eaten (e.g. see exam