Attaching Directly to a Program
Note
This article applies to Visual Studio 2015. If you're looking for the latest Visual Studio documentation, see Visual Studio documentation. We recommend upgrading to the latest version of Visual Studio. Download it here
Users who want to debug programs in a process that is already running typically follow this process:
In the IDE, choose the Debug Processes command from the Tools menu.
The Processes dialog box appears.
Choose a process and click the Attach button.
The Attach to Process dialog box appears, listing all debug engines (DEs) installed on the machine.
Specify the DEs to use to debug the selected process, and then click OK.
The debug package starts a debug session and passes the list of DEs to it. The debug session in turn passes this list, along with a callback function, to the selected process, and then asks the process to enumerate its running programs.
Programmatically, in response to the user request, the debug package instantiates the session debug manager (SDM) and passes the list of selected DEs to it. Along with the list, the debug package passes the SDM an IDebugEventCallback2 interface. The debug package passes the list of DEs to the selected process by calling IDebugProcess2::Attach. The SDM then calls IDebugProcess2::EnumPrograms on the port to enumerate the programs running in the process.
From this point on, each debug engine is attached to a program exactly as detailed in Attaching After a Launch, with two exceptions.
For efficiency, DEs that are implemented to share an address space with the SDM are grouped so that each DE has a set of programs it will attach to. In this case, IDebugProcess2 calls IDebugEngine2::Attach and passes it an array of programs to attach to.
The second exception is that the startup events sent by a DE attaching to a program that is already running do not typically include the entry point event.