Hi Delve team,
I'm currently using Delve in VS Code, and appreciating the Disassembly view a lot.
When debugging code at the assembly level, it's often useful to be able to see the contents of memory at a given location, particularly when trying to resolve addresses from values in registers.
This is possible, for example, in the LLDB C/C++ extension. VS Code offers a "Vew hex binary" button in the Variables panel, which opens a hex view of the memory location (screenshots attached).
As the Delve DAP adapter does not support reading memory, when this is required, I need to switch back to using the Delve CLI, and the examinemem command.
In order to support memory viewing in DAP, Delve would need to:
* set supportsReadMemoryRequest capability to true
* implement the onReadMemoryRequest handler
* return a memoryReference for each variable in the VariablesResponse
Given the memory features from the CLI and the GDB adapter, I'm assuming this is feasible. Does this seem like an interesting feature? I'm going to start working on this, let me know if you have any guidance, recommendations, or caveats I haven't thought of.
Cheers,
Charlie