In general, if you encounter any errors, it's worth increasing the verbosity of etwprof's output with either -v or -d (the latter is more verbose; see Usage for details).
If you encounter any crashes, please create a minidump (you can instruct Windows Error Reporting to automatically create a dump for you), open a GitHub issue, and attach the dump with potential repro steps included.
If you believe the result .etl file etwprof produced is incorrect, check if WPR/xperf handles your scenario correctly. If you are on Windows 8 or later, it's best to run WPR/xperf and etwprof in parallel:
- Start tracing with WPR/xperf
- Start tracing with etwprof
- Perform your scenario
- Stop tracing with both tools
- Compare the two .etl files
If you don't see your specific problem in the trace recorded by WPR/xperf, then chances are there is a bug in etwprof. Please file a GitHub issue, and attach a trace of your scenario recorded with xperf. We might be able to repro the problem with --emulate (see Usage for details). As traces may contain personal information, it's best not to upload them to a publicly accessible location.