jasonmolenda wrote: I am uncertain where I should detect an improperly formatted memory range. It could be in `Process::GetMemoryRegionInfo`, which would catch a bad gdb remote serial protocol response as well. Or it could be localized to IRMemoryMap::FindSpace if we only wanted to avoid an infinite loop in that one place -- but there are other parts of the code that try to iterate over the address space in the target with these objects. This patch adjusts it in the most specific place that fixed the issue I was looking at, to start with.
https://github.com/llvm/llvm-project/pull/115963 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
