Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Recently We have a production issue with application freezed, we tried to break in and analyse the dump file, unfortunately the call stack for the dump file does not looks good and hard to track down the cause of the freeze.
If the application hung rather than crashed, try loading into windbg and run
!analyze -v -hangor try using adplus in hang mode. This tries to determine the cause of the hang which should give you a more meaningful call stack. The!lockscommand can be useful too if you have deadlock by showing you what is blocking on a resource.