- data breakpoint
See processor breakpoint.
- DbgEng extension
A debugger extension based on the prototypes in the dbgeng.h header file. These extensions use the debugger engine API to communicate with the debugger engine.
- debug build
See Checked Build.
A debugger engine application that uses the full functionality of the debugger engine. For example, WinDbg, CDB, NTSD, and KD are debuggers.
- debugger console
A fictional entity representing the source of the debugger engine input and the destination of its output. In reality, the debugger engine only uses input and output callbacks and has no notion of what is being used to implement them.
Typically, input is received from the Debugger Command window and output is sent to the same window. However, the input and output callbacks can provide many other sources of input and destinations for output, for example, remote connections, script files, and log files.
- debugger engine
A library for manipulating debugging targets. Its interface is based on the prototypes in the dbgeng.h file. It is used by debuggers, extensions, and debugger engine applications.
- debugger engine API
A powerful interface to control the behavior of the debugger engine. It may be used by debuggers, DbgEng extensions, and debugger engine applications. The prototypes for this interface are found in the dbgeng.h header file.
- debugger engine application
A stand-alone application that uses the debugger engine API to control the debugger engine.
- debugger extension
An external function that can run inside the debugger. Each extension is exported from a module known as an debugger extension DLL. The debugger engine invokes the debugger extension by calling its code within the DLL. Some debugger extensions ship with Debugging Tools for Windows. You can write your own extensions to automate any number of debugger features or to customize the output of the information accessible to the debugger.
Also referred to as an , or simply .
- debugger extension DLL
A DLL containing debugger extensions. When the debugger engine loads the DLL these extensions become available for use within the debugger.
- debugger extension library
See debugger extension DLL.
- debugging client
An instance of the debugger engine acting as a proxy, sending debugger commands and I/O to the debugging server.
- debugging server
An instance of the debugger engine acting as a host, listening for connections from debugging clients.
- debugging session
The debugging session is the actual act of running a software debugging program, such as WinDbg, KD, or CDB, to debug a software component, system service, application, or operating system. The debugging session can also be run against a memory dump file for analysis.
A debugging session starts when a acquires a and lasts until all targets have been discarded.
- default exception filter
The event filter which applies to exception events that do not match any other exception filters. The default exception filter is a specific exception filter.
- dormant mode
A state in which a debugger program is running, but without a target or active session.
- downstream store
A cache of symbols created by a symbol server. Typically this cache is on your local machine, while the symbol store is located remotely. If you have a chain of symbol servers, the downstream store can be located on any computer downstream from the symbol store.
- dump file
See crash dump file.
- dump target
A crash dump file that is being debugged.