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

[Felipe de Azevedo Piovezan via lldb-commits]

================
@@ -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:

For example:

> This is
different than the absence of the `dirty_pages` key, which means
that this stub cannot provide information about pages of memory
being modified or not.

This is not said in `qMemoryRegionInfo`, but it probably also applies there.

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