Update docs: Linux dump analysis in a Windows environment

[kajr0s]

Documentation Request

I'm trying to figure out how to analyze managed Linux dumps in a Windows environment. The documentation makes it clear that this can be done in Visual Studio, WinDbg and dotnet-dump. But I find reliable confirmation of this only for Visual Studio, starting with version 16.8.

WinDbg states that as of version 1.0.1908.30002, all core windows and commands should work correctly, but most extensions and Windows-specific commands will not work (https://learn.microsoft.com/en-us/windows-hardware /drivers/debugger/windbg-release-notes). It turns out that it will not be possible to fully use the SOS extension in WinDbg to analyze Linux dumps.

For the dotnet-dump tool, it is mentioned everywhere that the 'dotnet-dump analyze' command only works in the environment where the dump was collected. But the article (https://learn.microsoft.com/en-us/dotnet/core/diagnostics/debug-linux-dumps#analyze-dumps-on-windows) does not mention any restrictions.

I don't know what to believe.

Previous documentation

https://learn.microsoft.com/en-us/dotnet/core/diagnostics/debug-linux-dumps#analyze-dumps-on-windows

Dumps collected from a Linux machine can also be analyzed on a Windows machine using Visual Studio, Windbg, or the dotnet-dump tool.

[hoyosjs]

@kajr0s Have you tried either SOS under WinDBG or under dotnet-dump? The dotnet-dump docs are a little stale, analyzing from windows is indeed possible. On windbg, SOS commands should largely work (some things like dumpccw and such wont, since they are not particularly useful there). I dont see anything in the WinDBG docs that suggests otherwise.

[tommcdon]

Docs seem to have been updated, closing