New submission from Frank Ch. Eigler <f...@elastic.org>: Similar to https://bugs.python.org/issue31574, it would be useful the the interpreter allowed a tracing tool to hook the PyCFunction_Call() site, maybe via the C_TRACE() macro, kind of how it already does in _PyEval_EvalFrameDefault(). This would help diagnose problems in the C upcalls.
---------- components: Interpreter Core messages: 310278 nosy: fche priority: normal severity: normal status: open title: Add dtrace hook for PyCFunction_Call type: performance _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue32599> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
