Hi Mark, Thanks for gathering this proposal! Looks very interesting. I have some preliminary questions: how is this going to affect the "py-bt" command of the gdb helpers (https://github.com/python/cpython/blob/master/Tools/gdb/libpython.py#L1876-L1897) and other similar tools that produce a unified Python-C backtrace? There are several debuggers that rely on the fact that they can merge the C stack and the Python stack by substituting every call to "_PyEval_EvalFrameDefault" and friends for the respective Python frame obtained separately or by inspecting the frame object in the stack (like gdb does).
Is this change going to affect these tools or they will continue working as before? In case this change will affect this tools, is there any workaround to produce the unified C/Python call stack given the Python stack and the C stack? Kind regards, Pablo Galindo Salgado _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/27DON4D7Y3WMFMOT7OV6D4LD6QUXXQRB/ Code of Conduct: http://python.org/psf/codeofconduct/
