Question

I’m working on an application that has a software watchdog. If some thread locks up, or is in a wait for more than a minute, the watchdog causes an exception in order to pull down the application and restart it.

So I’m looking at dumpfiles whose faulting stack is pointing at the watchdog thread. I need to identify the real faulting thread.

I’m looking for general advice and a possible strategy for using windbg to identify the real faulting thread.

Answer 1

In dump files you don’t have information you are looking for (cpu usage history), but you can list all threads and examine stack. This will most probably help because the thread that caused the closed should be blocked in wait or something like that