locked
Cannot debug CrashReport from Dashboard - How to find the problem source?

    Question

  • Hi,

    I have released the first version of my first Windows Store app just a few days ago. Today I discovered that is a CrashDump listed in the Reports/Quality section of the Dashboard. I dowloaded the CrashDump and tried to find the source of the problem using WinDbg by following this instruction: http://blogs.msdn.com/b/ntdebugging/archive/2014/01/13/debugging-a-windows-8-1-store-app-crash-dump.aspx

    I was able to follow the instruction almost up to the end but then the sos library is not found:

    0:006> .sympath SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols ... 0:006> .exr -1 ExceptionAddress: 769eb1d7 (combase+0x000fb1d7) ExceptionCode: c000027b ExceptionFlags: 00000001 NumberParameters: 2 Parameter[0]: 03f3f32c Parameter[1]: 00000001 0:006> !error c000027b Error code: (NTSTATUS) 0xc000027b (3221226107) - Anwendungsinterne Ausnahme. 0:006> .ecxr eax=03f3f030 ebx=00000000 ecx=00000000 edx=00000000 esi=03f3f360 edi=03f3f030 eip=769eb01f esp=03f3f314 ebp=03f3f3bc iopl=0 nv up ei pl nz ac po nc cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000212 combase+0xfb01f: 769eb01f 6a03 push 3 0:006> knL *** Stack trace for last set context - .thread/.cxr resets it
    ...

    0:006> dt 03f3f32c combase!_STOWED_EXCEPTION_INFORMATION_HEADER*
    0x05f182e4
       +0x000 Size             : 0x28
       +0x004 Signature        : 0x53453032

    0:006> .formats 0x53453032
    Evaluate expression:
      Hex:     53453032
      Decimal: 1397043250
      Octal:   12321230062
      Binary:  01010011 01000101 00110000 00110010
      Chars:   SE02
      Time:    Wed Apr 09 13:34:10 2014
      Float:   low 8.46917e+011 high 0
      Double:  6.90231e-315

    0:006> dt -a1 03f3f32c combase!_STOWED_EXCEPTION_INFORMATION_V2* [0] @ 03f3f32c --------------------------------------------- 0x05f182e4 +0x000 Header : _STOWED_EXCEPTION_INFORMATION_HEADER +0x008 ResultCode : 80131500 +0x00c ExceptionForm : 0y01 +0x00c ThreadId : 0y000000000000000000010001100101 (0x465) +0x010 ExceptionAddress : 0x76943bff Void +0x014 StackTraceWordSize : 4 +0x018 StackTraceWords : 0xa +0x01c StackTrace : 0x04c6c010 Void +0x010 ErrorText : 0x76943bff "趍ﯰ???" +0x020 NestedExceptionType : 0x314f454c +0x024 NestedException : 0x05f1be44 Void 0:006> !error 80131500 Error code: (HRESULT) 0x80131500 (2148734208) - <Unable to get error code text> 0:006> dpS 0x04c6c010 La 7697a9f1 combase!RoOriginateLanguageException+0x3b [d:\blue_gdr\com\combase\winrt\error\error.cpp @ 1083] 63da3bc6 mscorlib_ni+0x9b3bc6 63e41976 mscorlib_ni+0xa51976 63e415c1 mscorlib_ni+0xa515c1 5b72f9df System_Runtime_WindowsRuntime_ni+0x1f9df 5b72f965 System_Runtime_WindowsRuntime_ni+0x1f965 6372de66 mscorlib_ni+0x33de66 5b72f934 System_Runtime_WindowsRuntime_ni+0x1f934 5b6bff16 Windows_UI_ni+0x9ff16 64492a36 clr!COMToCLRDispatchHelper+0x28 0:006> !sos.pe The call to LoadLibrary(sos) failed, Win32 error 0n2 "The system cannot find the file specified." Please check your debugger configuration and/or network access. 0:006> .loadby sos clr The call to LoadLibrary(c:\symbols\clr.dll\52E0B78469b000\sos) failed, Win32 error 0n126 "The system cannot find the file specified." Please check your debugger configuration and/or network access.

    I does not have experience with this kind of debugging and without the instruction I would not have known any of the commands that I had to use in WinDbg.

    Does anyone have an idea how to go on from here?

    I have uploaded the CrashDump to my OneDrive. Would be great if anyone with more experience could have a look at it:
    http://1drv.ms/1gZzrRK

    Thank you very much!

    Monday, May 19, 2014 12:20 PM

Answers

  • Hi Agenor,

    By repro, I meant to say, can you reproduce the problem by yourself or is this only a customer reported issue (which can only have the mini-dump file)?

    If you can reproduce the problem yourself using Visual Studio, then when the exception happens, you should see an option in Visual Studio --> Tools where you can "Save Dump as"...to save the dump file. If you see that option then you can save the dump file and analyze the issue further.


    Windows Store Developer Solutions, follow us on Twitter: @WSDevSol|| Want more solutions? See our blog

    Tuesday, May 27, 2014 11:14 PM
    Moderator

All replies

  • Hi Agenor,

    You have debugged the issue as much as possible, but since this is a mini-triage dump, you cannot load SOS and perform managed code debugging. If you have a repro of the issue, you could probably collect a user dump with full memory (.dump /ma option in windbg) and then perform the managed code debugging.

    Otherwise...the exception seems to be happening inside mscorlib, so try checking for places in your code where you might not be handling a managed exception.

    Thanks,

    Prashant


    Windows Store Developer Solutions, follow us on Twitter: @WSDevSol|| Want more solutions? See our blog

    Tuesday, May 20, 2014 1:10 AM
    Moderator
  • Hi Prashant,

    thank you very much for your reply! It is good to know that I have done nothing wrong :-) As mentioned before I have very little experience in debugging Windows Store Apps and in using WinDbg. What exactly do you mean with "a repo I can use to collect user dump"?

    Of course I have the (unchanged) source code, all binaries and PDBs of the current app version that exhibits these crashes. Can I use these files to create a complete dump?

    One user report a crash to my e-mail support. Is there any way this user can extract a crash report from his system?

    I just checked the Dashboard to see if there are any new/other crash reports but I was very suprised to see that there are no reports listed any more. How can this be?

    Edit:
    Is it somehow possible to send a changed version to the user to let him test if the changes influence the problem?

    • Edited by Agenor Tuesday, May 20, 2014 1:37 PM
    Tuesday, May 20, 2014 5:55 AM
  • Hi Agenor,

    By repro, I meant to say, can you reproduce the problem by yourself or is this only a customer reported issue (which can only have the mini-dump file)?

    If you can reproduce the problem yourself using Visual Studio, then when the exception happens, you should see an option in Visual Studio --> Tools where you can "Save Dump as"...to save the dump file. If you see that option then you can save the dump file and analyze the issue further.


    Windows Store Developer Solutions, follow us on Twitter: @WSDevSol|| Want more solutions? See our blog

    Tuesday, May 27, 2014 11:14 PM
    Moderator