locked
Re: How can I see the stack trace from the .mdmp file? RRS feed

  • Question

  • Hi can any one tell me what to do?

    I have also tried it from the very begining as described earlier in this post. After getting another fresh crashdump from WER I have opened it in windbg; gives me following verbose output:

    Microsoft (R) Windows Debugger  Version 6.6.0007.5
    Copyright (c) Microsoft Corporation. All rights reserved.

    Extracted D:\Users\proseon\AppData\Local\Temp\00000f680_minidump.mdmp from
        D:\Users\proseon\Desktop\WERdump\0336830021.cab

    Loading Dump File [D:\Users\proseon\AppData\Local\Temp\00000f680_minidump.mdmp]
    User Mini Dump File: Only registers, stack and portions of memory are available

    Windows Vista Version 6000 UP Free x86 compatible
    Product: WinNt, suite: SingleUserTS
    Debug session time: Mon Apr  9 17:33:41.000 2007 (GMT+5)
    System Uptime: 0 days 1:11:20.989
    Process Uptime: 0 days 0:00:54.000
    Symbol search path is: E:\Windows\Symbols;C:\WER\Symbols_967;D:\Windows\System32
    Executable search path is: C:\WER\images_967;D:\Windows\System32
    ...............................................................................................
    Loading unloaded module list
    ....
    This dump file has an exception of interest stored in it.
    The stored exception information can be accessed via .ecxr.
    (844.ffc): CLR exception - code e0434f4d (first/second chance not available)
    eax=c0c0c0c0 ebx=769b817b ecx=00000005 edx=00000000 esi=0021d7e8 edi=00000000
    eip=77d80f34 esp=0021d788 ebp=0021d7a0 iopl=0         nv up ei pl zr na pe nc
    cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000246
    ntdll!KiFastSystemCallRet:
    77d80f34 c3              ret
    Verbose mode ON.

    After that I used kb command

    0:000> kb
      *** Stack trace for last set context - .thread/.cxr resets it
    ChildEBP RetAddr  Args to Child             
    0021ea18 79f9691a e0434f4d 00000001 00000001 kernel32!RaiseException+0x58
    0021ea78 7a098e88 0410de54 00000000 00000000 mscorwks!RaiseTheExceptionInternalOnly+0x226
    0021eb3c 638128b4 0410d5f8 00000000 0410de54 mscorwks!JIT_Throw+0xfc
    0021eb54 6381297a 790d7eb4 0410d8b0 03de1f28 System_Xml_ni+0x728b4
    0021eb70 639baf6a 00000000 0410ce68 0410d41c System_Xml_ni+0x7297a
    00000000 00000000 00000000 00000000 00000000 System_Xml_ni+0x21af6a

    can't understand what to do with this stacktrace which is not understandable for me at all.

    After that I used .ecxr command

    0:000> .ecxr
    eax=0021e9c8 ebx=03a36c48 ecx=00000001 edx=00000000 esi=0021ea50 edi=e0434f4d
    eip=7698b09e esp=0021e9c8 ebp=0021ea18 iopl=0         nv up ei pl nz ac po nc
    cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000212
    kernel32!RaiseException+0x58:
    7698b09e c9              leave

    After that I used .exr -1 command

    0:000> .exr -1
    ExceptionAddress: 7698b09e (kernel32!RaiseException+0x00000058)
       ExceptionCode: e0434f4d (CLR exception)
      ExceptionFlags: 00000001
    NumberParameters: 1
       Parameter[0]: 80131940

    After that I used !error e0434f4d

    0:000> !error e0434f4d
    Error code: (NTSTATUS) 0xe0434f4d (3762507597) - <Unable to get error code text>

    so what should I do with these outputs to get stacktrace in understandable format?

    • Moved by Max Wang_1983 Tuesday, April 26, 2011 5:34 PM forum consolidation (From:Windows Error Reporting for ISVs)
    Wednesday, May 2, 2007 5:48 AM

Answers

  •  

    [Splitting thread to discuss CLR-debugging.]

     

    Ved,

     

    For CLR debugging you need to load the SOS module into Windbg with the .load command. This will look something like this:

    .load C:\windows\Microsoft.Net\Framework\v2.0.50727\SOS.dll

     

    Once the SOS module is successfully loaded, you can use the !CLRStack command to get the managed callstack or

    !PrintException <exaddr> command to print the exception information.

     

    A full reference is avaiable here:

    http://msdn2.microsoft.com/en-us/library/bb190764(vs.80).aspx

     

    -saarp

    Wednesday, May 2, 2007 6:28 PM

All replies

  •  

    [Splitting thread to discuss CLR-debugging.]

     

    Ved,

     

    For CLR debugging you need to load the SOS module into Windbg with the .load command. This will look something like this:

    .load C:\windows\Microsoft.Net\Framework\v2.0.50727\SOS.dll

     

    Once the SOS module is successfully loaded, you can use the !CLRStack command to get the managed callstack or

    !PrintException <exaddr> command to print the exception information.

     

    A full reference is avaiable here:

    http://msdn2.microsoft.com/en-us/library/bb190764(vs.80).aspx

     

    -saarp

    Wednesday, May 2, 2007 6:28 PM
  • Hi saarp,
    Thanks for response.
    After loading SOS.dll, !PrintException gives me the stacktrace which I want.
    So at last I get whatever I want.
    Thanks againg for the solution.
    Monday, May 7, 2007 11:49 AM