Closed Aaronmsv closed 4 years ago
SOS for Linux dumps on Windows isn't supported for 2.1. It is only supported for 3.1.7 and recent 5.0 builds (not sure if the latest preview is supported). This feature is still in a preliminary stage. There are also some windbg fixes coming that may also be necessary for this to work end-to-end.
/cc: @sdmaclea
Ah I see, I'll setup a Linux VM to analyze the dump then. Thanks!
Hello, I would like to get some assistance on how to analyze a .NET Core 2.2.8 Linux dump on Windows with WinDbg. I'm not sure this is the right repository, but any help is appreciated.
I've worked with WinDbg multiple times in the past when the dump was generated on Windows and that worked fine, but I'm stuck with this Linux dump. Directly after opening the dump I get a very long list of warnings. This is a small snippet of that:
With
!sym noisy
I also see a lot of these:What I usually do afterwards for Windows .NET Core dumps is loading
coreclr.dl
andsos.dll
(.load C:\Program Files\dotnet\shared\Microsoft.NETCore.App\2.2.8\coreclr.dll
). Then, when I run e.g.!dumpheap -stat
I now get the following error:I have everything together in one folder that contains:
We've created the dump like this:
/usr/share/dotnet/shared/Microsoft.NETCore.App/2.2.8/createdump -u 1
I've also tried lldb on Mac (don't have much experience here), where I get a similar error:
I do have sos installed and libcoreclr.dylib is located at
/usr/local/share/dotnet/shared/Microsoft.NETCore.App/2.2.8/libcoreclr.dylib
. I've tried this withsetclrpath
, but that didn't solve it.Any suggestions on how I should continue?