Update Microsoft.Diagnostics.Tracing.TraceEvent to version 3.1.23 to fix P/Invoke buffer handling

[Copilot]

This PR updates the Microsoft.Diagnostics.Tracing.TraceEvent library from version 3.1.21 to 3.1.23 to incorporate the fix for an off-by-one error in buffer handling during P/Invoke operations.

Changes Made

• Updated MicrosoftDiagnosticsTracingTraceEventVersion from 3.1.21 to 3.1.23 in eng/Versions.props

Tools Affected

This centralized version update automatically applies to all diagnostic tools that use the TraceEvent library:

• ✅ dotnet-stack (specifically mentioned in the issue)
• ✅ dotnet-gcdump (specifically mentioned in the issue)
• ✅ dotnet-counters
• ✅ dotnet-trace
• ✅ dotnet-dsrouter

Note: dotnet-dump does not directly reference the TraceEvent library, so it is not affected by this change.

Background

The fix addresses a critical off-by-one error in buffer handling during P/Invoke operations that was resolved in TraceEvent version 3.1.23. This issue was originally reported and fixed in microsoft/perfview#2226.

By updating to the latest version, all affected diagnostic tools will now benefit from this important stability fix.

Fixes #5508.

Warning

Firewall rules blocked me from connecting to one or more addresses

I tried to connect to the following addresses, but was blocked by firewall rules:

• kijvsblobprodcus387.vsblob.vsassets.io
  • Triggering command: dotnet restore src/Tools/dotnet-stack/dotnet-stack.csproj (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to my firewall allow list

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.