Menu
Since UWP requires .Net Native (which is very welcome), I'm getting cryptic stack-traces now. This is the exception reported by people using my app:
System.InvalidCastException: InvalidCast_Com
at SharedLibrary!<BaseAddress>+0x429e9d
at SharedLibrary!<BaseAddress>+0x47d878
at SharedLibrary!<BaseAddress>+0x48455a
at SharedLibrary!<BaseAddress>+0x499043
at SharedLibrary!<BaseAddress>+0x498fb7
at SharedLibrary!<BaseAddress>+0x5ea468
at SharedLibrary!<BaseAddress>+0x5ea418
// this goes on...
I understand there's an invalid cast somewhere... but I need to know what SharedLibrary!<BaseAddress>+0x429e9d is pointing to.
Is there a way to find where these links point to?
835
Visually trace the call stack In Visual Studio Enterprise (only), you can view code maps for the call stack while debugging. In the Call Stack window, open the shortcut menu. Choose Show Call Stack on Code Map (Ctrl + Shift + `).
Analyze external stack traces From the main menu, select Code | Analyze Stack Trace or Thread Dump. In the Analyze Stack Trace dialog that opens, paste the external stack trace or thread dump into the Put a stacktrace here: text area. Click OK. The stack trace is displayed in the Run tool window.
To get a stack trace when a specific message is issued by the server or storage agent, enable the message for stack trace. Issue the MSGSTACKTRACE ENABLE < messageNumber > command to enable one or more messages for stack trace. Remember: < messageNumber > might be a space-delimited list of message numbers.
There is a tool in GitHub that can decipher .Net Native stack traces into human readable format.
https://github.com/dotnet/corefx-tools/tree/master/src/StackParser
107
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
