CDB can analyze binary code by disassembling it and displaying assembly instructions. With CDB, you can display and execute program code, set breakpoints, and examine and change values in memory. It works well across a network (using a remote access server), as it is character-based. In the case of a failing application, CDB can be used to obtain a stack trace or to look at the guilty parameters. It can be used to investigate the behavior of a working application. In fact, CDB is fully capable of debugging both console applications and graphical Windows programs.ĬDB is extremely powerful for debugging a program that is currently running or has recently crashed (live analysis), yet simple to set up. The name Console Debugger is used to indicate the fact that CDB is classified as a console application it does not imply that the target application must be a console application. Microsoft Console Debugger (CDB) is a character-based console program that enables low-level analysis of Windows user-mode memory and constructs. It is identical to KD in every way, except that it spawns a new text window when it is started, whereas KD inherits the Command Prompt window from which it was invoked. There is a variation of the KD debugger named NTKD. You need two computers (the host computer and the target computer) for kernel-mode debugging. Typically, KD does not run on the computer being debugged.

KD also supports multiprocessor debugging. You can use KD to debug kernel-mode components and drivers, or to monitor the behavior of the operating system itself. Microsoft Kernel Debugger (KD) is a character-based console program that enables in-depth analysis of kernel-mode activity on all NT-based operating systems. WinDbg is a graphical-interface counterpart to CDB/NTSD and to KD/NTKD. WinDbg also supports various remote debugging options for both user-mode and kernel-mode targets. Its Debugger Command window allows the user to issue a wide variety of commands.įor kernel-mode debugging, WinDbg typically requires two computers (the host computer and the target computer). WinDbg can view source code, set breakpoints, view variables (including C++ objects), stack traces, and memory. It can access any symbol or variable from a module that has PDB symbol files, and can access any public function's name that is exposed by modules that were compiled with COFF symbol files (such as Windows. WinDbg uses the Visual Studio debug symbol formats for source-level debugging. WinDbg provides debugging for the Windows kernel, kernel-mode drivers, and system services, as well as user-mode applications and drivers. Microsoft Windows Debugger WinDbg (Classic) is a Windows-based debugger that is capable of both user-mode and kernel-mode debugging. WinDbg is using the same underlying engine as WinDbg (Classic), so all the commands, extensions, and workflows you're used to will still work as they did before.įor more information, see WinDbg Features WinDbg (Classic) WinDbg is the latest version of WinDbg with modern visuals, faster windows, a full-fledged scripting experience, built with the extensible debugger data model front and center. The following sections describe the debugging environments. There are six available debugging environments:

Microsaoft script debugger