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.

classification
Title: Add dtrace hook for PyCFunction_Call
Type: enhancement Stage:
Components: Interpreter Core Versions:
process
Status: open Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: 0mp, BTaskaya, christian.heimes, fche, nanjekyejoannah, vstinner
Priority: normal Keywords:

Created on 2018-01-19 17:39 by fche, last changed 2022-04-11 14:58 by admin.

Messages (2)
msg310278 - (view) Author: Frank Ch. Eigler (fche) Date: 2018-01-19 17:39
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.
msg358776 - (view) Author: Batuhan Taskaya (BTaskaya) * (Python committer) Date: 2019-12-21 18:47
If there are no objections, I can work on a patch.
History
Date User Action Args
2022-04-11 14:58:56adminsetgithub: 76780
2021-08-10 10:25:060mpsetnosy: + 0mp
2019-12-28 18:23:42nanjekyejoannahsetnosy: + nanjekyejoannah
2019-12-21 18:47:11BTaskayasetnosy: + vstinner, christian.heimes, BTaskaya
messages: + msg358776
2018-01-19 23:19:24pablogsalsettype: performance -> enhancement
2018-01-19 17:39:36fchecreate