I have a store app that has a crash reported, actually several. I downloaded the triagedump file and opened it using windbg. Using the technique described by Matt Small here -- http://blogs.msdn.com/b/wsdevsol/archive/2013/08/15/dump-diving-into-cert-failure_3a00_--how-to-get-a-good-callstack-from-triagedump.dmp.aspx -- I got a call stack that was not very informative. (Note: in addition to what Matt Small describes, I used the .sympath+ command to point to the program's pdb file.)
I then used the technique described here -- http://blogs.msdn.com/b/ntdebugging/archive/2014/01/13/debugging-a-windows-8-1-store-app-crash-dump.aspx -- to get the following stored exception information:
0x07f2ac44
+0x000 Header : _STOWED_EXCEPTION_INFORMATION_HEADER
+0x008 ResultCode : 80131508
+0x00c ExceptionForm : 0y01
+0x00c ThreadId : 0y000000000000000000010001011111 (0x45f)
+0x010 ExceptionAddress : 0x77cf42ad Void
+0x014 StackTraceWordSize : 4
+0x018 StackTraceWords : 0x3a
+0x01c StackTrace : 0x0592f640 Void
+0x010 ErrorText : 0x77cf42ad "붨鏷???"
+0x020 NestedExceptionType : 0x314f454c
+0x024 NestedException : 0x07f58aec Void
[1] @ 0833f06c
---------------------------------------------
0x08535760
+0x000 Header : _STOWED_EXCEPTION_INFORMATION_HEADER
+0x008 ResultCode : 80131508
+0x00c ExceptionForm : 0y01
+0x00c ThreadId : 0y000000000000000000000000000000 (0)
+0x010 ExceptionAddress : (null)
+0x014 StackTraceWordSize : 4
+0x018 StackTraceWords : 0x35
+0x01c StackTrace : 0x08588ccc Void
+0x010 ErrorText : (null)
+0x020 NestedExceptionType : 0
+0x024 NestedException : (null)
The first stowed exception has a nested exception of type LE01 (STOWED_EXCEPTION_NESTED_TYPE('LEO1')) which I would like to be able to take a look at, but I do not know how. Presumably I would use a dt command, but I would need to know the name of the language exception object that windbg would understand.
Can anybody help me?