Earlier this week I got an email from a reader who had a hang in an application and sent in some Debug Diag logs.
In order for me to dig in deeper I would need to open a support case as I would have to ask follow up questions and look at the dumps etc. However, I wanted to show some interesting details from his report to show you how to move forward if you get an issue like that.
Analyzing the debug diag output
At the top of the report generated by debug diag for the dump, you will see an analysis summary section.
In this section Debug Diag will report any issues that it found in the dump. This is based on a set of common issues that debug diag looks for.
Note: Debug Diag is so not looking for any managed (.net) issues in the standard hang/crash analysis scripts, so what you will see here is mostly if there are any native causes for the hang/crash, such as locked critical sections, waiting on socket c ...
Go to the complete details ...