OS Access (Windows CE 5.0)
The OS Access component provides OS awareness to the debugger. It is a host-side component, implemented as service like eXDI. Typically, the OS Access service interacts between a client, such as Platform Builder, and the eXDI service. Clients that need OS awareness use the OS Access service, rather that calling the eXDI service directly.
In the case of the software probe KdStub, assistance and acceleration is provided by a target-side OS Access component, OsAxs.
With OS Access, a client can obtain information about active processes, threads, and modules. In addition, OS Access exposes a simplified symbol-handling interface called IMiniSH. For more advance symbol information, see DIA interface.
The following table provides examples of commonly used interfaces that are part of the OS Access component.
| Interface | Description |
|---|---|
| IOsAxsProcess | Provides information about current processes, including enumerating threads owned by a specified process and enumerating modules used by the process. |
| IOsAxsEnumProcess | Enumerates the active IOxAxsProcess interfaces, resets an enumeration sequence, or to clones an entire enumeration. |
| IOsAxsThread | Gets the call stack, and reads and writes thread context registers. |
| IOsAxsEnumThread | Enumerate the active IOxAxsThread interfaces, resets an enumeration sequence, or to clones an entire enumeration. |
| IOsAxsModule | Acquires all the data required for unwinding a routine. |
| IOsAxsEnumModule | Enumerates the active IOxAxsModule interfaces, resets an enumeration sequence, or to clones an entire enumeration. |
| IOsAxsClientModuleEvents | Notifies a debugging client that a module has been loaded or unloaded. |
See Also
eXDI Run-State Control | Memory and Register Access | eXDI Driver Development
Send Feedback on this topic to the authors