09.02.2014 Views

Windows sysinternals

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

218 Part II Usage Guide<br />

■ Shared WS The amount of Shareable WS that is currently shared with other processes.<br />

■ Locked WS The amount of memory that has been guaranteed to remain in physical<br />

memory and not incur a page fault when accessed.<br />

■ Blocks The number of individually allocated memory regions.<br />

■ Largest In Summary View, the size of the largest contiguous memory block for that<br />

allocation type.<br />

■ Address In Details View, the base address of the memory region in the process’<br />

virtual address space.<br />

■ Protection In Details View, identifies the types of operations that can be performed<br />

on the memory. In the case of top-level allocations that show expandable sub-blocks,<br />

Protection identifies a summary of the types of protection in the sub-blocks. An access<br />

violation occurs on an attempt to execute code from a region not marked Execute (if<br />

DEP is enabled), to write to a region not marked Write or Copy-on-Write, or to access<br />

memory that is marked as no-access or is only reserved but not yet committed.<br />

■ Details In Details View, additional information about the memory region, such as the<br />

path to its backing file, Heap ID (for Heap memory), Thread ID (for Stack memory), or<br />

.NET AppDomain and Garbage Collection generations.<br />

Note The VirtualProtect API can change the protection of any page to something different from<br />

that set by the original memory allocation. This means that there can potentially be pages of<br />

memory private to the process in a shareable memory region, for instance, because the region<br />

was created as a pagefile-backed section, but then the application or some other software<br />

changed the protection to copy-on-write and modified the pages.<br />

Timeline and Snapshots<br />

VMMap retains a history of snapshots of the target process’ memory allocation state. You<br />

can load any of these snapshots into the VMMap main view and compare any two snapshots<br />

to see what changed.<br />

When tracing an instrumented process, VMMap captures snapshots automatically. You can<br />

set the automatic capture interval to 1, 2, 5, or 10 seconds from the Options | Trace Snapshot<br />

Interval submenu. You can pause and resume automatic snapshots by pressing Ctrl+Space,<br />

and manually capture a new snapshot at any time by pressing F5.<br />

When you analyze a running process instead of launching an instrumented one, VMMap<br />

does not automatically capture snapshots. You must manually initiate each snapshot by<br />

pressing F5.<br />

www.it-ebooks.info

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!