Hello folks,
Due to various changes in Python 3.11 and PEP 669 in Python 3.12 dtrace/systemtap support is in a semi-functional state. Some probes are essentially missing and some tests are broken.
There have been some issues and attempts to fix it but haven’t moved far, e.g.:
Missing DTrace probes · Issue #104280 · python/cpython · GitHub
Some DTrace probes are broken in 3.11 · Issue #98894 · python/cpython · GitHub
gh-125914: Clean up the dtrace code and documentation for the hook is not using by Zheaoli · Pull Request #126246 · python/cpython · GitHub
GH-98894: Fix `function__return` and `function__entry` dTrace probe missing after `GH-103083` by Zheaoli · Pull Request #125019 · python/cpython · GitHub
However after reading the comments around these issues, it looks there’s a worry that dtrace probes could be a performance bottleneck for the JIT and it could also be a pain to keep them maintained through the various performance work on CPython.
So my question is, given that dtrace support is not fully functional right now, should it be completely removed? Or would a coordinated effort to resolve the issues be considered?
Buildbots are not currently testing the --with-dtrace builds, I can definitely add the option for the ones I maintain.