More QoL information to get regarding memory regions

[Argentix03]

• Parsing the process's PE headers and import tables to determine which DLLs are loaded and which functions are being used. This can help identify memory regions that are being used for code or data from a particular DLL.

• Examining the stack and heap to identify memory regions that are being used for local variables, function arguments, or dynamically allocated memory.

• Examining the process's page file to identify memory regions that are backed by a file, which may indicate that the region is being used for memory-mapped I/O.

• Examining the process's thread contexts to identify memory regions that are being used for thread stacks.

• Examining the process's handle table to identify memory regions that are being used for shared memory or other inter-process communication mechanisms.

[Argentix03]

Thread stack addresses can be treated as a negative insight ( [-] Stack Address). Heap not sure yet if can be useful until I understand it better.