Debug tasks
To debug a program, it must be launched and a debug engine (DE) must be attached to it, or else the DE must be attached to a previously launched program. Once attached, the DE must generate certain startup events. In response, the debug package attempts to bind the breakpoints set in the IDE. When the program hits a bound breakpoint, it halts and waits for user input.
In this section
Security issues discusses the security steps that are needed to debug a program.
Launch a program provides step-by-step instructions on how to specify a DE, which calls the operating system to launch the program.
Attach directly to a program describes the process used to debug a program in a process that is already running.
Send startup events after a launch lists the events that take place once the DE is attached to the program, until the program is at its main entry point and is ready for debugging.
Control of execution explains how the DE typically sends an entry-point event, a load-complete event, or a stopping event, depending on the circumstances.
Bind breakpoints describes how, if the user sets a breakpoint, the IDE formulates the request and prompts the debug session to create the breakpoint.
Evaluate expressions explains how expressions are created and what happens when an expression is evaluated.
Visualize and view data explains how type visualizers and custom viewers are supported by the expression evaluator (EE).
Related sections
Debugger concepts describes the main debugging architectural concepts.
Debugger components provides an overview of the Visual Studio debugging components, which include the DE, EE, and symbol handler (SH).
Debugger contexts explains how the DE operates simultaneously within code, documentation, and expression evaluation contexts. Describes, for each of the three contexts, the location, position, or evaluation relevant to it.