Home Page (Objects) | Overview | FAQ | Reference
With the Debugger object, you can inspect the processes being debugged in Developer Studio.
The Debugger object has the following properties and methods:
| Properties | |
| Application | Parent |
| Breakpoints | RemoteProcedureCallDebugging |
| DefaultRadix | State |
| JustInTimeDebugging |
| Methods | |
| Evaluate | ShowCurrentStatement |
| Go | StepInto |
| Restart | StepOut |
| RunToCursor | StepOver |
| SetNextStatement | Stop |
The Debugger object has the following event:
Using a Dual Interface to Access This Object
This section about dual interfaces is useful for writing add-ins or automating Developer Studio across processes. This section is not applicable to writing VBScript macros.
The Debugger object implements the IDebugger dual interface. Through this interface, add-ins can directly access the members (properties, methods, and events) of this object and can employ early binding to make calls into these members faster at run time.
Add-ins written in Visual C++ can access members of the Debugger object by using the header files in Vc98\Include\objmodel. However, if you use the Developer Studio Add-in Wizard to create an add-in, the wizard automatically includes these header files in your source code.
The following table shows the header files you need for the Debugger object:
| Header file | Description |
| dbgauto.h | Declares the dual interfaces. |
| dbgguid.h | Declares the GUIDs used to identify the interfaces. |
| dbgdefs.h | Declares additional information needed to use the interfaces, such as error IDs and enumerated constants. |
Add-ins written in Visual Basic can access members of the Debugger object by using the Visual Studio '97 Debugger type library, located in Msdev98\bin\ide\devdbg.pkg.
Note Visual Studio '97 Debugger is the name that appears in the Visual Basic References dialog box.