clairetokyo
New Member
We sent this dump to MS and they sent us back these results. I am trying to replicate this so that we can find out why the web app crashed on a different server. My comments start with @@@. Any help is greatly appreciated.\[code\]0:025> !critlist @@@ *This command is no longer available so I used !locks*CritSec at 786dd8e0. Owned by thread 25. \[/code\] thread 25 is holding the critical section (or lacking) and below are the threads are waiting on it. Impact of this lock @@@ I can reproduce this in Debug Diag Tool 70.42% of threads blocked (Threads 15 30 31 32 33 34 35 36 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 134 135 138) -- checking the call stack: \[code\]:025> kLChildEBP RetAddr 0285fcc4 7c827b69 ntdll!KiFastSystemCallRet0285fcc8 77e6202c ntdll!ZwWaitForMultipleObjects+0xc0285fd70 77e62fbe kernel32!WaitForMultipleObjectsEx+0x11a0285fd8c 79f8e39a kernel32!WaitForMultipleObjects+0x180285fdac 79f8e48c mscorwks!SVR::WaitForFinalizerEvent+0x770285fdc0 79e9caff mscorwks!SVR::GCHeap::FinalizerThreadWorker+0x490285fdd4 79e9ca9b mscorwks!ManagedThreadBase_DispatchInner+0x4f0285fe68 79e9c9c1 mscorwks!ManagedThreadBase_DispatchMiddle+0xb10285fea4 79f20508 mscorwks!ManagedThreadBase_DispatchOuter+0x6d0285fecc 79f20519 mscorwks!ManagedThreadBase_NoADTransition+0x320285fedc 79f220eb mscorwks!ManagedThreadBase::FinalizerBase+0xd0285ff14 79f0e255 mscorwks!SVR::GCHeap::FinalizerThreadStart+0xbb0285ffb8 77e6482f mscorwks!Thread::intermediateThreadProc+0x490285ffec 00000000 kernel32!BaseThreadStart+0x34\[/code\] -- rebuild the stack: @@@I am unable to find out how to rebuild the stack to produce the results below. I need to know which DLL is causing the lock. In this example secSSo.dll. Once i find out I can use command lmvm to find the owner of the thread. \[code\]0285dc00 000000000285dc04 000b7a800285dc08 23000003*** ERROR: Symbol file could not be found. Defaulted to export symbols for secSSO.dll - secSSO!SSOStartLogin+0x8d6f40285dc0c 0285dc740:025> lmvm secSSOstart end module name22f70000 23036000 secSSO (export symbols) secSSO.dll Loaded symbol image file: secSSO.dll Image path: C:\Program Files\Business Objects\Common\2.8\bin\secSSO.dll Image name: secSSO.dll Timestamp: Sun Oct 14 01:39:17 2007 (4711AB85) CheckSum: 000C83D4 ImageSize: 000C6000 File version: 10.5.0.1943 Product version: 10.5.0.1943 File flags: 8 (Mask 3F) Private File OS: 4 Unknown Win32 File type: 1.0 App File date: 00000000.00000000 Translations: 0409.04b0 CompanyName: Business Objects ProductName: Crystal Enterprise InternalName: Crystal Enterprise OriginalFilename: Crystal Enterprise ProductVersion: 10.5.0.1943 FileVersion: 10.5.0.1943 FileDescription: Crystal Enterprise LegalCopyright: Copyright (C)1995-2007 Business Objects LegalTrademarks: Crystal Enterprise (tm) is a trademark of Business Objects\[/code\] -- so either thread 25 already leaked the Criticalsection or doing nothing, and rest of the threads are just waiting on it.