Tip - It is possible to analyze threads and critical sections of process when it is in the hanged state.
Details - Follow the below steps.
1. Generate dump file of the hanged process using ProcDump(see References) utility.
2. Open the Dump file in Windbg
3. Using !locks WinDbg command, we can list the critical sections in a dump, the thread ID of the thread owning the lock, and the number of threads waiting to acquire it.
4. Select lock owning thread View->Process and Threads menu of windbg
5. View the stack of selected thread using View->Call Stack
6. Using View menu, we can see the debug info like variables,… of selected thread.
7. Thus we can analyze all threads that own lock
References-
ProcDump - http://technet.microsoft.com/en-us/sysinternals/dd996900.aspx
http://www.microsoft.com/whdc/devtools/debugging/default.mspx
http://blogs.technet.com/b/markrussinovich/archive/2010/08/24/3351213.aspx
Posted by - Binu Jose
Details - Follow the below steps.
1. Generate dump file of the hanged process using ProcDump(see References) utility.
2. Open the Dump file in Windbg
3. Using !locks WinDbg command, we can list the critical sections in a dump, the thread ID of the thread owning the lock, and the number of threads waiting to acquire it.
4. Select lock owning thread View->Process and Threads menu of windbg
5. View the stack of selected thread using View->Call Stack
6. Using View menu, we can see the debug info like variables,… of selected thread.
7. Thus we can analyze all threads that own lock
References-
ProcDump - http://technet.microsoft.com/en-us/sysinternals/dd996900.aspx
http://www.microsoft.com/whdc/devtools/debugging/default.mspx
http://blogs.technet.com/b/markrussinovich/archive/2010/08/24/3351213.aspx
Posted by - Binu Jose
http://www.wintellect.com/CS/blogs/jrobbins/archive/2010/06/17/how-to-capture-a-minidump-let-me-count-the-ways.aspx
ReplyDeletegood
ReplyDelete