IeXdi2Exec::GetCurrentExecMode (Windows CE 5.0)
This method returns the active processor mode.
HRESULT GetCurrentExecMode( DWORD dwCpuNum DWORD* pdwExecMode);
Parameters
dwCpuNum
[in] CPU number.This parameter should be 0 if the CPU is not a symmetric multi-processor platform (SMP). Otherwise, assign dwCpuNum a value between 0 and n-1, where n is the CPU number in the SMP system.
pdwExecMode
[out] Pointer to the active CPU processor mode.For example, the trap op-code may be different in 16-bit mode than in 32-bit mode on processors such as ARM and MIPS that have two modes.
By convention, the processor mode should be 0 for 32-bit mode (default), and 1 for 16-bit mode.
Return Values
The following table shows return values for this method.
| Value | Description |
|---|---|
| S_OK | Indicates the function was successful. |
| E_FAIL | Indicates an unspecified failure. |
| E_NORESAVAILABLE | Indicates a breakpoint resource was not available and the method cannot instantiate all breakpoints. |
| E_OUTOFMEMORY | Indicates an out of memory error. |
| E_INVALIDARG | Indicates one or more invalid arguments. |
| EXDI_E_COMMUNICATION | Indicates a communication error between host driver and debugging target. |
Remarks
The Auto-EBP Skip feature of eXDI uses this method. The op code allows the eXDI service to resume execution from an embedded breakpoint without requiring the client to move the target instruction pointer to the next instruction.
The eXDI service keeps a list of embedded breakpoint (EBP) op codes. Only one EBP can be used for setting a software breakpoint in each execution mode specified by pdwExecMode.
Requirements
OS Version: Windows CE 5.0 and later.
Header: eXDI2.h.
Link Library: ole32.lib, oleaut32.lib.
See Also
Send Feedback on this topic to the authors