In this episode of Defrag Tools, Andrew Richards, Chad Beeder and Larry Larsen walk you through a Windows Store Application crash dump. We show the Quality page of the Dev Dashboard and debug a dump with WinDbg.
[00:38] - Quality Reports
[06:08] - Stowed Exceptions (Error Code 0xC000027B)
[08:50] - .ecxr & k -- View the stack of the exception
[11:05] - !analyze -v -- Analysis is limited
[13:39] - .exr -1 -- Get the error code and parameters
[15:28] - !sos.pe (a.k.a. !sos.PrintException) -- Print the Last CLR Exception
[16:38] - !procdumpext.deep 1 !sos.pe -- Run !pe on each stack
[19:34] - Does the HResult match the Error Code?
[20:06] - .exr -1 -- Use Parameter #0 and #1
[20:25] - dp <ptr> -- Display Pointers (dp)
[20:45] - dp poi(<ptr>) -- Display Pointers (dp) at Pointer (poi)
[21:35] - dd poi(<ptr>) -- Display DWORDs (dd) at Pointer (poi)
[23:58] - Email us your issues at firstname.lastname@example.org
- If the error code doesn't match, use !error <code> to get the description
- Not all crashes in CLR apps are caused by an unhandled CLR Exception
If you have a crash you don't understand, email the CAB file to email@example.com and we'll help you.
Available formats for this video:
Actual format may change based on video formats available and browser capability.
Comments have been closed since this content was published more than 30 days ago, but if you'd like to send us feedback you can Contact Us.