I tried to debug an user mode program that is crashing. Everything goes well
(in WinDBG) until the program actually crash. The Windbg process takes all
CPU but still respond (somewhat) for some seconds before locking
completelly.
Commands, locals, Disassembly, call stack, processes and threads and memory
are shown. Only Disassembly and call stack are filled with information.
The target is a VC6 compiled program with PDB infos. I then tried remotely
with DbgSrv but WinDbg still lock up like when I tried locally. Target is
W2K and second is XP. Both are 6.3.0017.0. No symbols, source or bin path
are set.
Here the stack trace of the locked thread: (made with a second instance of
WinDBG hooked up to the first)
0:001> kv
ChildEBP RetAddr Args to Child
WARNING: Stack unwind information not available. Following frames may be
wrong.
0098fe34 02080129 0000000a 0098fe84 00000003 dbgeng!DebugCreate+0x3fe1
0098fea4 01014c17 00269f68 00000018 0000000a dbgeng!DebugCreate+0x4339
0098ff50 01030ae5 002690e8 00000042 0098ff94 windbg+0x14c17
0098ff60 0103246b 0223cb8c 00268fb0 002690ec windbg+0x30ae5
0098ff94 0101eba7 00000000 804fa821 f8235c9c windbg+0x3246b
0098ffb4 7c80b50b 00000000 5f0113d4 00ffffff windbg+0x1eba7
0098ffec 00000000 0101e9a0 00000000 00000000 kernel32!BaseThreadStart+0x37
(FPO: [Non-Fpo])