Debugging application crash/hang in production environments
Here's a nice blog post (with lots of screen shots!) detailing how to grab a stack from a crashing or hung application. Note that in the typical case we'll get a Watson report, so customers don't normally need to do this kind of manual operation for a crash, but it's very useful info if you need to know the stack, for instance, in discussing the bug in a forum posting.
http://blogs.msdn.com/msdnts/archive/2006/11/24/how-to-debug-application-crash-hang-in-production-environment.aspx
A common tough scenario is the application crash/hang in production environment. Production environment is different from development environment that it normally does not have any powerful tools to obtain information regarding application failure. In this blog entry, I will talk about 2 wonderful tools to help collect information in production environment: Windbg and Process Explorer.
