This repository has been archived by the owner on Jul 27, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 49
ETW Tracing using rusttrace crate #38
Comments
Hey Codri - were you able to receive logging information from the core as well? I'm mostly interested in the errors, as currently they are ignored, but this might be a useful solution. (See #60) |
Hey @LiHRaM , No, I didn't wire it up for core. Only for requests/responses going from/into xi-win.
So, long story short, ETW and LTTng are interesting pieces of technology, can be a great fit for high performance crossplatform tracing. But, I'm yet to make the thin wrapper library that can log into both. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
I've wired up rusttrace(https://github.com/flowerinthenight/rusttrace) crate in xi-win ui.
It's a small mess to setup(can make a powershell script to automate it), but can be handy for debugging, in absence of println!, also ETW events can be used by tools like perfview for profiling.
Was wondering if you see any value in a pull request for this, if not so I could avoid the trouble of signing google license agreements.
Here's an example trace as displayed in the command line by mftrace.
The text was updated successfully, but these errors were encountered: