3 ms·
I'll be surprised if this doesn't become an abandoned experiment. Take a look at the commit history: https://github.com/microsoft/DTrace-on-Windows/commits/win
by jiggawatts 4y ago
I'll be surprised if this doesn't become an abandoned experiment.
Take a look at the commit history: https://github.com/microsoft/DTrace-on-Windows/commits/windows https://github.com/microsoft/DTrace-on-Windows/commits/windo...
Last commit 4 months ago... and then a year ago... and then two years before that.
I saw this mentioned here a while back and saw the "last commit 2 years ago" status in GitHub and just ignored it completely. It's most likely someone's pet project with no real support in the larger Microsoft corp.
Oh and I tried it in a virtual machine, but it just blue screened, which doesn't inspire confidence.
- btschaegg 4y agoI am getting the same feeling, as Microsoft's track record with such things hasn't been stellar, anyway. A crucial point, however, is that Windows Server only has had a kernel new enough to support this for a little while (not counting previews and RCs for obvious reasons), which I'd say is the one Microsoft platform that would benefit the most from this. Also, since it's really hard for outsiders to find documentation on Windows kernel interna (which means as a normal user you'd be tracing syscalls at best), I suspect a key motivation was to improve observability for the Windows dev team, so we possibly also wouldn't be able to estimate of how much use the port really is.