Debugger Extension Functions (Compact 2013)
3/26/2014
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 help you control and examine the target device being debugged.
The following table shows debugger extension functions.
Programming element |
Description |
|---|---|
This function checks to see whether the user pressed the CTRL+C key combination. |
|
This function disassembles an instruction and stores a string in a buffer that can be printed. |
|
This function prints a formatted string to the command window for the debugger. |
|
This structure specifies stack frames for the StackTrace function. |
|
This function obtains the context of the process being debugged. |
|
This function retrieves information stored in a data block. |
|
This function returns the value of an expression. |
|
This function obtains or sets the search path for symbols. |
|
This function locates the symbol nearest to a specified address. |
|
This function is an entry point for a substantial amount of the functionality provided by the extension functions for the kernel debugger. |
|
This function reads a CPU-specific control space into an array. |
|
This function reads from system I/O locations. |
|
This function reads memory from the process being debugged. The entire memory must be accessible, or the operation will fail. |
|
This function reads from physical memory. |
|
This function sets the context of the process being debugged. |
|
This function specifies a thread to use for the next call to the StackTrace function. |
|
This function receives a stack trace for the process being debugged. |
|
This function writes to system I/O locations. |
|
This function writes memory to a process being debugged. The entire memory must be accessible, or the operation will fail. |
|
This function writes to physical memory. |