Memory and Register Access (Windows CE 5.0)
The eXDI provides OS-agnostic interfaces to directly read from and write to the target's main memory and registers. In addition, OS-aware interfaces provide access to in-process memory usage.
For more information about memory access that is independent of the OS, see OS-Agnostic Memory Handling.
For more information about in-process memory access, see OS-Aware Memory Handling.
For more information about managing register contents, see eXDI Register Access.
Memory Model
Platform Builder 5.0 assumes that the target platform's memory model consists of one linear virtual address space of 4 GB. In Windows CE-based systems, all processes share this unique address space.
In the particular case of x86 microprocessor-based systems, Windows CE disables memory segmentation, but enables page translation.
There is only one virtual address space at any time for all processes, but individual processes are protected from one another. If the specific microprocessor allows differentiation, the virtual address space is identical for both code and data.
The debugger engine API uses 64-bit addresses for extensibility when referring to memory locations on the target.
If the target uses 32-bit addresses, the native 32-bit address is not automatically sign-extended by the engine to 64-bit addresses.
See Also
Send Feedback on this topic to the authors