[Lldb-commits] [lldb] [lldb] Add a MemoryRegionInfo cache at a process stop (PR #202509)

Felipe de Azevedo Piovezan via lldb-commits lldb-commits at lists.llvm.org
Tue Jun 9 00:48:58 PDT 2026


================
@@ -819,6 +835,22 @@ which indicates that the register cannot be read at this current
 stop point, and lldb should not try to read the register value with
 a separate `p` read-register request, it will not succeed.
 
+`jThreadsInfo` is an array of thread-specific information, but some
+things we expedite are usually not thread-specific; this packet
+could have been structured as a Dictionary with a `threads` array
+and separate keys for non-thread specific things like this.
+
+`memory-region-info` is an array of memory region information; a
----------------
felipepiovezan wrote:

Should we just say:

> `memory-region-info` is an array of memory region information, with the exact same information that would have been returned by a `qMemoryRegionInfo` packet.

If not, what is different?
If they are the same, I feel like it's better to consolidate all the information (and any clarifications you want to make) in `qMemoryRegionInfo`.

https://github.com/llvm/llvm-project/pull/202509


More information about the lldb-commits mailing list