Defrag Tools: #64 - Windows 8.1 - Store App Crash (c000027b)

Sign in to queue

Description

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.

Resources:
Improving apps with Quality reports
Defrag Tools SkyDrive (inc. Scripts and ProcDumpExt)

Timeline:
[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:05] - JavaScript Exceptions (WWAJSE) - read the ErrorText* file in the CAB
[23:58] - Email us your issues at defragtools@microsoft.com
Note:
- 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 defragtools@microsoft.com and we'll help you.

Embed

Download

The Discussion

Add Your 2 Cents