================
@@ -288,8 +288,15 @@ Status ScriptedProcess::DoGetMemoryRegionInfo(lldb::addr_t
load_addr,
MemoryRegionInfo ®ion) {
Status error;
if (auto region_or_err =
- GetInterface().GetMemoryRegionContainingAddress(load_addr, error))
+ GetInterface().GetMemoryRegionContainingAddress(load_addr, error)) {
region = *region_or_err;
+ if (region.GetRange().GetRangeBase() == 0 &&
+ (region.GetRange().GetByteSize() == 0 ||
+ region.GetRange().GetByteSize() == LLDB_INVALID_ADDRESS)) {
----------------
jasonmolenda wrote:
We had a gdb stub returning {0, UINT64_MAX} the other week and it broke
IRMemory::FindSpace() which will avoid any memory region with
read/write/execute flags if qMemoryRegionInfo packets are supported. The stub
claimed the entire address space, FindSpace() said it could not find any
address range available, and all expressions broke.
Yeah, a range of {0, 1} would result in algorithms like FindSpace() looping for
a very long time, and be nearly as bad. But so far the two instances I've seen
of people return bad ranges are {0,0} and {0,UINT64_MAX}.
https://github.com/llvm/llvm-project/pull/115963
_______________________________________________
lldb-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
