-
-
Notifications
You must be signed in to change notification settings - Fork 47
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
dotnet stack frames for WER dumps are marked as 'unknown_image' #1342
Comments
I've looked into this a bit. The frame in question has no package, and we don't extract any module from the minidump that covers address |
Just to make sure it wasn't related to the minidump itself or etc. I checked with
|
I think the main problem is, that the C# module gets JITed to the heap, where |
Thanks for the additional details, that's very helpful. It might take us a bit to get to the bottom of this. |
This might actually be the case that we fundamentally do not support .NET minidumps. |
Environment
Version: 23.11.2
Windows 11
.Net 8 (But also tested on .Net Framework)
.symboliclirc
Steps to Reproduce
2.1 Adding the debug symbols from the build does not change the output except for dotnet host unmanaged code
.\symbolicli.exe --offline .\crash.dmp
Expected Result
I would have expected those frames to contain the correct information about my dotnet functions.
Actual Result
The CLI outputs for dotnet stack frames, an 'unknown_image' frame:
I know that this is the dotnet frame due to its surrounding frames.
The full output of that dump is here:
test.json
Example build with crashing application is here:
build.zip
Example dump of that build is here:
CrashTestApp.exe.25308.dmp
The text was updated successfully, but these errors were encountered: