<trclass="memdesc:a10c9a4bb206872c102aaffac05a4d924"><tdclass="mdescLeft"> </td><tdclass="mdescRight">The number of memory regions present in the <aclass="el"href="structMINIDUMP__MEMORY__LIST.html#a7c2359575a803000e228bcdef33b42d0"title="Structures identifying each memory region present in the minidump file. ">MemoryRanges</a> array. <br/></td></tr>
<trclass="memdesc:a7c2359575a803000e228bcdef33b42d0"><tdclass="mdescLeft"> </td><tdclass="mdescRight">Structures identifying each memory region present in the minidump file. <br/></td></tr>
<divclass="textblock"><p>Information about memory regions within the process. </p>
<p>Typically, a minidump file will not contain a snapshot of a process’ entire memory image. For minidump files identified as <aclass="el"href="dbghelp_8h.html#a7580bc5aa0738de92a9766904fc7e79ba8be18b33190940c5ca447bd989eaf7c5"title="A minidump file without any additional data. ">MiniDumpNormal</a> in <aclass="el"href="structMINIDUMP__HEADER.html#a052f2280538826d030c4cb5154963e27"title="A bitfield containing members of MINIDUMP_TYPE, describing the types of data carried within this mini...">MINIDUMP_HEADER::Flags</a>, memory regions are limited to those referenced by <aclass="el"href="structMINIDUMP__THREAD.html#a4affab2d1a0995fdb085d302d78fbb81"title="A snapshot of the thread’s stack. ">MINIDUMP_THREAD::Stack</a> fields, and a small number of others possibly related to the exception that triggered the snapshot to be taken. </p>
</div><hr/>The documentation for this struct was generated from the following file:<ul>