Looks ProcDump dumps a post mortem dump of the wrong thread. Made ProcDump the JIT-debugger:
C:\>procdump -ma -i c:\mydumps
Made a test program C++ MFC:
int* ptr = 0;
switch(message) {
...
case IDM_CRASH:
*ptr = 23;
break;
...
Selecting the Crash item from the menu (of the program ProcDumpTest.exe), the application crashes and a dump is made. The dump however shows (windbg) a stack and an instruction pointer (eip = 7c90e514) of an unexpected thread. How to get the stack trace of thread where the error occurred?
00400000 - 004a0000 ProdDumpTest.exe
07c90000 - 07c9b000 ntdll.dll
Got the same problem in a more serious case. Thanks for any help! GMore
After the .reload /f command, the !analyze -v showed the correct information. Thanks for the help.