Missing DTrace probes #104280
Comments
|
I think DTrace was intentionally removed because it was not being used. I forgot where I read that, but Mark will have a better idea of it. |
|
I think a bigger issue is that I'm pretty sure it isn't tested on any CI jobs or buildbots, so stuff can break (like #98894) without us noticing. If it's not tested, it effectively isn't supported. Not sure whether the right path forward is for some motivated person to fix and maintain it, for us to remove the broken stuff and keep the working stuff (with a big disclaimer in the docs), or to just rip it out entirely. Anecdotally, it's always been a bit uncomfortable to touch this stuff when modifying the interpreter, since I'm not very sure how it works or how to test it. @ambv might have an idea of what the right path forward is here. |
Bug report
On Linux, you can list available DTrace probes by running /bcc/tools/tplist.py tool;
$ ~/bcc/tools/tplist.py -l cpython/python cpython/python python:function__entry cpython/python python:function__return cpython/python python:line cpython/python python:import__find__load__done cpython/python python:import__find__load__start cpython/python python:audit cpython/python python:gc__start cpython/python python:gc__doneThe
function__entry,function__returnandlineprobes appear to be missing after the GH-103082: Implementation of PEP 669: Low Impact Monitoring for CPython update.$ ~/bcc/tools/tplist.py -l cpython/python cpython/python python:import__find__load__done cpython/python python:import__find__load__start cpython/python python:audit cpython/python python:gc__start cpython/python python:gc__doneYour environment
The text was updated successfully, but these errors were encountered: