❔ Crash dump problem
Hello!
I have .NET 6 service that runs inside docker container on Linux Rocky. This service is crashes a lot of times with Segmentation fault and Linux creates crash dump that compressed inside zst file. I tried to analyze it with multiple tools such as WinDbg, Visual Studio, lldb, dotnet-dump without any success. Visual Studio: Heap information is not present and I can't run "Debug with Managed Only". Visual studio shows following message:"Managed debugging is not available for this minidump. The debuggee memory space does not have the expected debugging export table." WinDbg: : Can't understand anything from what it shows. See screenshot. LLDB, dotnet-dump: When trying to run clrstack it fails because it can't find libmscordaccore.so file even though it is present and I changed symbol directory where this file is present. Also I tried to create crash dumps inside container and it worked but only when it is not Segmentation fault. I will glad if anybody can help me. Maybe you know how to create crash dump on segmentation fault or how can I actually analyze Linux created dump.
I have .NET 6 service that runs inside docker container on Linux Rocky. This service is crashes a lot of times with Segmentation fault and Linux creates crash dump that compressed inside zst file. I tried to analyze it with multiple tools such as WinDbg, Visual Studio, lldb, dotnet-dump without any success. Visual Studio: Heap information is not present and I can't run "Debug with Managed Only". Visual studio shows following message:"Managed debugging is not available for this minidump. The debuggee memory space does not have the expected debugging export table." WinDbg: : Can't understand anything from what it shows. See screenshot. LLDB, dotnet-dump: When trying to run clrstack it fails because it can't find libmscordaccore.so file even though it is present and I changed symbol directory where this file is present. Also I tried to create crash dumps inside container and it worked but only when it is not Segmentation fault. I will glad if anybody can help me. Maybe you know how to create crash dump on segmentation fault or how can I actually analyze Linux created dump.
5 Replies
Was Rocky glibc or musl based?
I am not sure how can I check it. This is what i got after checking linux version:
from https://docs.rockylinux.org/release_notes/9_2/#updated-system-toolchain i would imply its glibc
That looks like a crash in the CLR itself and not in managed code
Was this issue resolved? If so, run
/close - otherwise I will mark this as stale and this post will be archived until there is new activity.