Debugging Using Visual Studio
Starting with Windows Driver Kit (WDK) 8, the driver development environment and the Windows debuggers are integrated into Microsoft Visual Studio. In this integrated environment, most of the tools you need for coding, building, packaging, testing, debugging, and deploying a driver are available in the Visual Studio user interface.
Typically kernel-mode debugging requires two computers. The debugger runs on the host computer, and the code being debugged runs on the target computer. The target computer is also called the test computer. You can do user-mode debugging on a single computer, but in some cases you might want to debug a user-mode process that is running on a separate target computer.
In the Visual Studio environment, you can configure target computers for kernel-mode and user-mode debugging. You can establish a kernel-mode debugging session. You can attach to a user-mode process or launch and debug a user mode process on the host computer or a target computer. You can analyze dump files. In Visual Studio you can sign, deploy, install, and load a driver on a target computer.
These topics show you how to use Visual Studio to perform several of the tasks involved in debugging a driver.
- Debugging a User-Mode Process Using Visual Studio
- Opening a Dump File Using Visual Studio
- Kernel-Mode Debugging in Visual Studio
- Ending a Debugging Session in Visual Studio
- Setting Symbol and Executable Image Paths in Visual Studio
- Remote Debugging Using Visual Studio
- Entering Debugger Commands in Visual Studio
- Setting Breakpoints in Visual Studio
- Viewing the Call Stack in Visual Studio
- Source Code Debugging in Visual Studio
- Viewing and Editing Memory and Registers in Visual Studio
- Controlling Threads and Processes in Visual Studio
- Configuring Exceptions and Events in Visual Studio
- Keeping a Log File in Visual Studio
Build date: 4/9/2013