❔ How to take a native crash [{0x7f803bba7228} + 0x3bd] + PDB/DLL and get a line number?
I have a native crash from a .net application on macOS that contains some managed code in the stack.
10 MyDll.MyClass.Myfunction (string,string) [{0x7f803bba7228} + 0x3bd] [/xyz/MyDll/MyClass.cs :: 378u] (0x14b362550 0x14b362c88) [0x7f8032105240 - MyApp.exe] [0x14b36290d]
I have the DLL and PDB and I'd like to turn this into a line number. How can I do that?
14 Replies
!clrstack in windbg should give you the line numbers if the symbols are good
Assuming you actually have a memory dump or are live debugging
I don't have either this is a user's crash from our crash reporter. I have stack + offsets + build.
Is this not supposedly showing the line number?
xyz/MyDll/MyClass.cs :: 378u
I haven't seen a crash error in that format before
I thought it might be but 378 is the closing } of a try and nothing else
Is it a release build?
The line numbers can be off.
It is ya, crash is from microsoft error reporting for mono
You generally can't get the exact line number for a release build. It should be in the general vicinity though.
The line before is a reasonable line to have triggered a native crash
Calls sqlite eventually
That's probably it
Thanks, I guess the answer is right there.
Maybe u just means unsigned? I was thinking offset in bytes from method start or something....
I would guess it means unsigned although I'm not positive.
Thanks for taking a look
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.