The tricky part here was that the exisiting implementation of WriteAllRegisters was expecting
hex-encoded data (as that was what the first implementation I replaced was using, but here we had
binary data to begin with. I thought the read/write register functions would be more useful if
they handled the hex-encoding themselves (all the other client functions provide the responses in
a more-or-less digested form). The read functions return a DataBuffer, so they can allocate as
much memory as they need to, while the write functions functions take an llvm::ArrayRef, as that
can be constructed from pretty much anything.
Details
Details
- Reviewers
clayborg - Commits
- rGb42b48e051e9: Remove the last manually constructed packet from gdb-remote register context +…
rLLDB279232: Remove the last manually constructed packet from gdb-remote register context +…
rL279232: Remove the last manually constructed packet from gdb-remote register context…
Diff Detail
Diff Detail