© 2004 Microsoft Corporation. All rights reserved.
Figure 2 SYMSTORE.EXE Command Line Switches

Switch
Explanation
Add
Adds files to a symbol server
/f File
Adds a particular file or directory
/r
Adds files or directories recursively
/s Store
Root directory of the symbol store
/t Product
Name of the product
/v Version
Product version
/o
Verbose output helpful for debugging
/?
Help output
Figure 5 The DBGENG.DLL Debugging Engine Interfaces

Interface
Description
IDebugAdvance
Offers control over the complete processor context. IDebugRegisters is the higher-level interface to processors, but this interface is complete control.
IDebugBreakpoint
Interface for setting and retrieving breakpoint information.
IDebugClient2
Main interface for attaching or creating processes, connecting to remote debuggers, or opening dump files.
IDebugControl2
Interface for controlling the debugger and handling such disparate items as output, disassembly, processor information, setting breakpoints, and exception processing. The methods of this interface essentially match up with WinDBG.
IDebugDataSpaces2
Interface to retrieve key offset locations and data from kernel mode.
IDebugEventCallbacks
Interface for callback items from the debug engine such as breakpoints being hit, thread creation/termination, and module loads/unloads.
IDebugInputCallbacks
Allows the debugging engine to get input from and clients attached. This interface assumes that there is some sort of user interaction.
IDebugOutputCallbacks
Interface that all output from the debug client goes through.
IDebugRegisters
Interface for handling registers in a platform-neutral manner.
IDebugSymbolGroup
Interface to handle groups of symbols delineated by scope.
IDebugSymbols2
Symbol engine interface that handles module information, type information, scope setting, and symbol lookup.
IDebugSystemObjects2
Interface for retrieving thread and process information, such as handle and ID values, for the debuggee.

Home
Topics
Issues
Columns
Downloads
Subscribe
Contact Us

MSDN Magazine