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
Describe the bug With .NET Core 6.0 !socket and $ipaddress function do not work.
To Reproduce Dump a .NET 6 or higher process which has some web request hanging around
Expected behavior !socket and $ipaddress should work. Looks like the internal offsets have changed.
!wfrom -type System.Net.Sockets.Socket select $addr(),_remoteEndPoint._address._addressOrScopeId,$ipaddress(_remoteEndPoint._address._addressOrScopeId) calculated: 0000015481B356B0 _remoteEndPoint._address._addressOrScopeId: 0n768473354 calculated: #INVALID# calculated: 0000015481B39C70 _remoteEndPoint._address._addressOrScopeId: 0n768473354 calculated: #INVALID# calculated: 0000015481B3F118 _remoteEndPoint._address._addressOrScopeId: 0n768473354 calculated: #INVALID#
Desktop (please complete the following information):
How do you build the project. On my machine it complains about error C1083: Cannot open type library file: '..\ClrMemDiagExt\bin\x86\Debug\NetExtShim.tlb': No such file or directory
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the bug
With .NET Core 6.0 !socket and $ipaddress function do not work.
To Reproduce
Dump a .NET 6 or higher process which has some web request hanging around
Expected behavior
!socket and $ipaddress should work. Looks like the internal offsets have changed.
Desktop (please complete the following information):
How do you build the project. On my machine it complains about
error C1083: Cannot open type library file: '..\ClrMemDiagExt\bin\x86\Debug\NetExtShim.tlb': No such file or directory
The text was updated successfully, but these errors were encountered: