We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When adding a std::uint64_t field to an ETW event with TraceLoggingValue is seen as a long rather than ulong when using TraceEvent.PayloadByName.
std::uint64_t
long
ulong
TraceEvent.PayloadByName
I haven't checked if the same happens with other integer types and/or when using manifest-based event.
The text was updated successfully, but these errors were encountered:
Can you share example trace file (so it's faster to try it on my side)?
Sorry, something went wrong.
No branches or pull requests
When adding a
std::uint64_t
field to an ETW event with TraceLoggingValue is seen as along
rather thanulong
when usingTraceEvent.PayloadByName
.I haven't checked if the same happens with other integer types and/or when using manifest-based event.
The text was updated successfully, but these errors were encountered: