diff options
author | Michal Gorny <mgorny@gentoo.org> | 2019-04-30 16:30:32 +0000 |
---|---|---|
committer | Michal Gorny <mgorny@gentoo.org> | 2019-04-30 16:30:32 +0000 |
commit | d14a0de9ad073f02ef10dc4a7c8d7b372c85c7e3 (patch) | |
tree | 15b98ee30b8fb2e820aec24fed7c1ade2000841c /lldb/packages/Python/lldbsuite/test | |
parent | 68924e6be7cda3e06fad5229949329e8f5624d57 (diff) | |
download | bcm5719-llvm-d14a0de9ad073f02ef10dc4a7c8d7b372c85c7e3.tar.gz bcm5719-llvm-d14a0de9ad073f02ef10dc4a7c8d7b372c85c7e3.zip |
[lldb] [Process/NetBSD] Fix handling piod_len from PT_IO calls
Fix bugs in piod_len return value processing in ReadMemory()
and WriteMemory() methods. In particular, add support for piod_len == 0
indicating EOF, and fix summing bytes_read/bytes_written when PT_IO does
partial reads/writes.
The EOF condition could happen if LLDB attempts to read past
vm.maxaddress, e.g. as a result of RBP containing large (invalid) value.
Previously, the 0 return caused the function to retry reading via PT_IO
indefinitely, effectively deadlooping lldb-server.
Partial reads probably did not occur in practice, yet they would cause
ReadMemory() to return incorrect bytes_read and/or overwrite previously
read data.
WriteMemory() suffered from analoguous problems.
Differential Revision: https://reviews.llvm.org/D61310
llvm-svn: 359572
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test')
0 files changed, 0 insertions, 0 deletions