Uh oh!
There was an error while loading. Please reload this page.
QUIC logging update - #55500
Conversation
ghost
commented
Jul 12, 2021
Tagging subscribers to this area: @dotnet/ncl Issue DetailsTogether with #55483 this updates all logging to use msquic handles instead of hash code - for listeners, connections and streams. The format of handle is the same as msquic one, e.g.:
|
ghost
commented
Jul 12, 2021
Tagging subscribers to this area: @dotnet/ncl Issue DetailsTogether with #55483 this updates all logging to use msquic handles instead of hash code - for listeners, connections and streams. The format of handle is the same as msquic one, e.g.:
|
wfurt
commented
Jul 12, 2021
Did you get the trace sample on Windows? Seems like different casing on pointers. I'm wondering if this is something intentional or something that can be fixed @nibanks. |
nibanks
commented
Jul 12, 2021
We use CLOG to convert the LTTng traces on Linux and generally netsh to convert the ETW traces on Windows. Right now, there's no guarantee that casing will be the same across everything. |
wfurt
commented
Jul 12, 2021
Improvement for CLOG? While you can use case insensitive text search it would be nice if this is as simple as possible. |
CarnaViire
commented
Jul 12, 2021
Yes; on Windows it's uppercase 🙁 |
Together with #55483 this updates all logging to use msquic handles instead of hash code - for listeners, connections and streams. The format of handle is the same as msquic one, e.g.: