IOsAxsMem::FillMemoryByProc (Windows CE 5.0)
This method fills memory with a block that matches a given sequence.
HRESULT FillMemoryByProc( [in] DWORDProcID,[in] LINEAR_MEM_MAP_TYPElmt,[in] ADDRESS_TYPEAddressRangeStart,[in] ADDRESS_TYPEAddressRangeEnd,[in] DWORDdwNbElem,[in] BYTEbAccessWidthInBytes,[in, size_is(dwNbElem * bAccessWidthInBytes)] BYTE* pbSequenceToFill);
Parameters
ProcID
Identifier of the process of interest.lmt
Linear memory map type.The following memory map types are used by convention:
Value Description LMM_VIRT, 0 Virtual memory LMM_PHYS, 1 Physical memory LMM_IO, 2 Peripheral I/O 3 and higher Free for custom use AddressRangeStart
Starting address of the memory block to be filled on the target device.AddressRangeEnd
Ending address of the memory block to be filled on the target device.*dwNbElem *
Number of elements of bAccessWidthInBytes to be filled.bAccessWidthInBytes
Data width in bytes, where byte=1, word=2, dword=4, and so on.pbSequenceToFill
Buffer containing the sequence to fill.This buffer must be at least as large as dwNbElem.
Warning
The server should handle sequence buffers of at least 1 KB.
Return Values
The following table shows return values for this method.
| Value | Description |
|---|---|
| S_OK | Indicates the function was successful and all breakpoints were created. |
| E_FAIL | Indicates an unspecified failure. |
| 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 target device. |
Remarks
The memory content provided to this function should be cleaned of software breakpoint artifacts and other memory modifications produced by the debugging activity of a driver, probe, or target device.
In general, the driver internal mechanism should be transparent to the client.
Requirements
OS Version: Windows CE 5.0 and later.
Header: OsAccess.h.
Link Library: OSAXSC.lib.
See Also
Send Feedback on this topic to the authors