The CLRMD APIs like stack trace, type resolution and GC heap dumping used by a dotnet-dump command for a Windows or Linux dumps may fail because the dump image may not contain the necessary module's data like metadata. The solution is to wrap the dump data reader's read memory functions and use the new memory service functions that find/download the runtime modules and maps them into the virtual address space.
The CLRMD APIs like stack trace, type resolution and GC heap dumping used by a dotnet-dump command for a Windows or Linux dumps may fail because the dump image may not contain the necessary module's data like metadata. The solution is to wrap the dump data reader's read memory functions and use the new memory service functions that find/download the runtime modules and maps them into the virtual address space.
This is similar to the problem described in issue https://github.com/dotnet/diagnostics/issues/503 for SOS commands.