Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate using native ETW APIs for recording traces #120

Open
randomascii opened this issue May 18, 2018 · 0 comments
Open

Investigate using native ETW APIs for recording traces #120

randomascii opened this issue May 18, 2018 · 0 comments

Comments

@randomascii
Copy link
Contributor

UIforETW currently requires that WPT be installed. When analyzing traces this makes sense, but for just recording traces this is a bit heavy handed. One reason for shelling out to xperf instead of using the ETW APIs directly is that the ETW APIs are the worst APIs ever made (reference: https://caseymuratori.com/blog_0025). However there are clean C++ wrappers for them that could be used:

https://github.com/Microsoft/krabsetw

Another reason for shelling out to xperf.exe is that when "show commands" is checked it is easy to see exactly what commands are issued and then create a batch file from them. I've done that.

This issue mostly exists in order to record the two links above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant