Open Kernel Crash Dumps in Visual Studio 11
The Performance Zone is presented by AppDynamics. Scalability and better performance are constant concerns for the developer and operations manager. Try AppDynamics' fully-featured performance tool for Java, .NET, PHP, & Node.js.
A dream is coming true. A dream where all the debugging you’ll ever do on your developer box is going to be in a single tool – Visual Studio.
In a later post, I will discuss device driver development in Visual Studio 11, which is another dream come true. For now, let’s take a look at how Visual Studio can open kernel crash dumps and perform crash analysis with all the comfy tool windows and UI that we know and love.
To perform kernel crash analysis in Visual Studio 11, you will need to install the Windows Driver Kit (WDK) on top of Visual Studio. Go on, I’ll wait here.
First things first – you go to File | Open Crash Dump, and you’re good to go:
Visual Studio will load that dump file and open the initial analysis window – which is a new tool called Debugger Immediate Window.
Note that the Threads window displays processors, and you can switch between processors to examine their call stack in the Call Stack window. Finally, if you’re dead serious and want to run some real debugger commands, there’s command-line IntelliSense for debugger commands, complete with a documentation tooltip.
In case you’re wondering, there is still room for WinDbg as a standalone tool. The obvious difference between WinDbg and Visual Studio – other than usability – is installation size. You can copy WinDbg over to a machine or run it from a USB stick, which is amazing in a production environment. So no, WinDbg isn’t redundant yet, but Visual Studio has just earned itself some street cred in the most hardcore debugging circles.