Programs

Applies to: Visual Studio Visual Studio for Mac

In the debugger architecture, a program:

• Is a container for both a set of threads and a set of modules. A program has no single analogy in the Windows operating system.

  A program is a kind of subprocess. For example, when you are debugging a Web site, a script can be seen as a program. While a script runs in the scripting engine process, independent of other scripts, it also has its own set of threads. A debug engine (DE) attaches to a program, and not to a process or a thread.

• Can identify itself and the process it's running in. A program can be attached to, be detached from, and describe the DE that created it, if any. A program can also execute, stop, continue, and be terminated.

• Can enumerate all its threads. A program can also supply its own disassembly stream, and can enumerate all the code contexts of a given document position.

• Is represented by an IDebugProgram2 interface, created before the program is attached, or as part of the attach process, depending on the implementation. When a port enumerates the programs of a process, each program is created in accordance with a corresponding IDebugProgramNode2 interface passed as an argument to AddProgramNode. While debug engines also create IDebugProgram2 interfaces to represent programs, these programs are not created in accordance with a program node. The IDebugProgramNode2 interfaces created by a DE are used for actual debugging, while those created by a port are used only for discovering which programs are running in a process.

See also

• Processes
• Program nodes
• Modules
• Debugger concepts
• Debug engine
• Document position
• Code context
• IDebugProgram2
• IDebugProgramNode2
• AddProgramNode