You can use functions that are exposed by the WDbgExts_CE.h header file in debugger extension commands. When developing a debugger extension, these functions can be helpful in controlling and examining the target device being debugged.

The following table shows debugger extension functions.

Programming element	Description
CheckControlC	This function checks to see whether the user pressed the CTRL+C key combination.
Disassm	This function disassembles an instruction and stores in a buffer a string that can be printed.
dprintf	This function prints a formatted string to the command window for the debugger.
EXTSTACKTRACE	This structure specifies stack frames for the StackTrace function.
GetContext	This function obtains the context of the process being debugged.
GetDebuggerData	This function retrieves information stored in a data block.
GetExpression	This function returns the value of an expression.
GetSetSympath	This function obtains or sets the search path for symbols.
GetSymbol	This function locates the symbol nearest to a specified address.
Ioctl	This function is an entry point for much of the functionality provided by the extension functions for the kernel debugger.
ReadControlSpace	This function reads a CPU-specific control space into an array.
ReadMemory	This function reads memory from the process being debugged. The entire area of memory must be accessible, or the operation fails.
ReadPhysical	This function reads from physical memory.
SetContext	This function sets the context of the process being debugged.
SetThreadForOperation	This function specifies a thread to use for the next call to the StackTrace function
StackTrace	This function receives a stack trace for the process being debugged.
WriteIoSpace	This function writes to system I/O locations.
WriteMemory	This function writes memory to a process being debugged. The entire area of memory must be accessible, or the operation fails.
WritePhysical	This function writes to physical memory.