XBDM currently uses getmem / setmem which transfers data as ASCII. For larger chunks this will be very slow too (more work + data conversion).
Additionally the memory hook for u8, u16 and u32 requires 3 network packets currently:
setmem
resume thread=workspace
getmem
This can be changed by directly modifying the xbdm packet instead of communicating through a memory bank. The command could also be extended to read and write data of arbitrary length to solve all issues of XBDM.
This is critical for streaming buffers back to a debugger as valuable time passes during these reads!
XBDM currently uses
getmem
/setmem
which transfers data as ASCII. For larger chunks this will be very slow too (more work + data conversion).Additionally the memory hook for u8, u16 and u32 requires 3 network packets currently:
This can be changed by directly modifying the xbdm packet instead of communicating through a memory bank. The command could also be extended to read and write data of arbitrary length to solve all issues of XBDM.
This is critical for streaming buffers back to a debugger as valuable time passes during these reads!