-
Notifications
You must be signed in to change notification settings - Fork 257
New issue
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
Execute ClrHeap.EnumerateRoots stops process with exit code 139 #1234
Comments
dotnet-dump has the same issue, as I understand it is based on ClrMD > dotnet-dump --version
8.0.506901+b0ee5b9a01e571161bf772aa659440a986bbe532
> dotnet-dump analyze /Users/ne4to/projects/dbg/dumps/coredump.37588 --command 'dumpheap -stat -live'
Loading core dump: /Users/ne4to/projects/dbg/dumps/coredump.37588 ...
Calculating live objects, this may take a while...
Caching GC roots, this may take a while.
Subsequent runs of this command will be faster.
[1] 43914 segmentation fault dotnet-dump analyze /Users/ne4to/projects/dbg/dumps/coredump.37588 --command |
I get this error intermittently on .NET 8.0.7, after connecting to a process and repeatedly enumerating thread stacktraces. Because it takes down the process, it makes cldmd essentially useless on macOS.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm trying to inspect a memory dump taken from a process running .NET 7.0.10, macos-arm64 (third party app).
When I try to iterate over ClrHeap.EnumerateRoots() my process exits without throwing any exception.
Console output:
Reproduced on latest Microsoft.Diagnostics.Runtime v3.1.456101 and v3.1.506101 from Azure DevOps public feed.
I tried to debug ClrMD and the process stops at the end of
ReadVirtual
method.clrmd/src/Microsoft.Diagnostics.Runtime/DacInterface/DacDataTargetCOM.cs
Lines 126 to 134 in 437022b
Last variable values:
Stack trace:
ClrMD is running in a .NET 8 process
dotnet --info output:
The text was updated successfully, but these errors were encountered: