News for hackers. Stuff that matters.

A comment on Tracers – Rust Instrumentation Library. Parent comment

Re:Tracers – Rust Instrumentation Library by anelson on Wednesday November 20, 2019 @01:41AM (#21581615)
Yes exactly. The goal of this project is to let authors put trace points in their code and at compile time target whatever tracing system makes sense. On Linux that's either systemtap or ltt-ng. On Windows it (will be; not implemented yet) the event tracing API, on MacOS and FreeBSD it would be dtrace. There's also an option to completely disable tracing at compile time, which removes all tracing code and imposes absolutely zero runtime overhead.
[ Parent | on HN ]
Re:Tracers – Rust Instrumentation Library by jen20 on Wednesday November 20, 2019 @12:02PM (#21585712)
Worth noting that DTrace is now available on Windows too as of "recently" [1][2]. It would be great to support that also!

[1]: https://www.microsoft.com/en-us/download/details.aspx?id=580...

[2]: https://github.com/microsoft/DTrace-on-Windows

[ Parent | on HN ]
Re:Tracers – Rust Instrumentation Library by anelson on Thursday November 21, 2019 @12:40AM (#21591720)
Cool! Assuming it's a faithful port with source-level compatibility, it should work with the existing DTrace implementation I'm building. The differences between compiler toolchains are already abstracted away by the excellent `cc` crate.

In any case I already have a Windows CI build; when DTrace is ready I'll add DTrace on Windows there and see what happens.

[ Parent | on HN ]
Re:Tracers – Rust Instrumentation Library by jen20 on Thursday November 21, 2019 @02:02AM (#21591999)
Great news, I'm very much looking forward to being able to use this crate! Thanks for your work (and that of those upstream of you).
[ Parent | on HN ]