<trclass="memdesc:af4b4a246ebfa54e57e4c953fb0c3dd31"><tdclass="mdescLeft"> </td><tdclass="mdescRight">The base address of the loaded module in the address space of the process that the minidump file contains a snapshot of. <br/></td></tr>
<trclass="memdesc:a701a839b502151638e18d66cc83445ee"><tdclass="mdescLeft"> </td><tdclass="mdescRight">The size of the loaded module. <br/></td></tr>
<trclass="memdesc:a9e034dc1c99bf014191f44c90ebe7bd4"><tdclass="mdescLeft"> </td><tdclass="mdescRight">The loaded module’s checksum, or <code>0</code> if unknown. <ahref="#a9e034dc1c99bf014191f44c90ebe7bd4">More...</a><br/></td></tr>
<trclass="memdesc:ae03bd3bf01de8e08c9a6abf37a9dfbbb"><tdclass="mdescLeft"> </td><tdclass="mdescRight">The module’s timestamp, in <code>time_t</code> units, seconds since the POSIX epoch, or <code>0</code> if unknown. <ahref="#ae03bd3bf01de8e08c9a6abf37a9dfbbb">More...</a><br/></td></tr>
<trclass="memdesc:a8aa1ae48a9a32640573747cba5a00274"><tdclass="mdescLeft"> </td><tdclass="mdescRight"><aclass="el"href="dbghelp_8h.html#acf465a1a77ecf067a9d946583bc6a3f8"title="An offset within a minidump file, relative to the start of its MINIDUMP_HEADER. ">RVA</a> of a <aclass="el"href="structMINIDUMP__STRING.html"title="A variable-length UTF-16-encoded string carried within a minidump file. ">MINIDUMP_STRING</a> containing the module’s path or file name. <br/></td></tr>
<trclass="memdesc:ac2babe58e6418124599ea2821f30bb84"><tdclass="mdescLeft"> </td><tdclass="mdescRight">The module’s version information. <br/></td></tr>
<trclass="memdesc:acd07e35faf066880eeabea8a91aa887a"><tdclass="mdescLeft"> </td><tdclass="mdescRight">A pointer to the module’s CodeView record, typically a link to its debugging information in <aclass="el"href="structcrashpad_1_1CodeViewRecordPDB70.html"title="A CodeView record linking to a .pdb 7.0 file. ">crashpad::CodeViewRecordPDB70</a> format. <ahref="#acd07e35faf066880eeabea8a91aa887a">More...</a><br/></td></tr>
<trclass="memdesc:a749bc0bb7492a1b9463631eec006b4d1"><tdclass="mdescLeft"> </td><tdclass="mdescRight">A pointer to the module’s miscellaneous debugging record, a structure of type <aclass="el"href="structIMAGE__DEBUG__MISC.html"title="Miscellaneous debugging record. ">IMAGE_DEBUG_MISC</a>. <ahref="#a749bc0bb7492a1b9463631eec006b4d1">More...</a><br/></td></tr>
<divclass="textblock"><p>Information about a specific module loaded within the process at the time the snapshot was taken. </p>
<p>A module may be the main executable, a shared library, or a loadable module.</p>
<dlclass="section see"><dt>See also</dt><dd><aclass="el"href="structMINIDUMP__MODULE__LIST.html"title="Information about all modules loaded within the process at the time the snapshot was taken...">MINIDUMP_MODULE_LIST</a></dd></dl>
</div><h2class="groupheader">Member Data Documentation</h2>
<p>The loaded module’s checksum, or <code>0</code> if unknown. </p>
<p>On Windows, this field comes from the <code>CheckSum</code> field of the module’s <code>IMAGE_OPTIONAL_HEADER</code> structure, if present. It reflects the checksum at the time the module was linked. </p>
<p>A pointer to the module’s CodeView record, typically a link to its debugging information in <aclass="el"href="structcrashpad_1_1CodeViewRecordPDB70.html"title="A CodeView record linking to a .pdb 7.0 file. ">crashpad::CodeViewRecordPDB70</a> format. </p>
<p>The specific format of the CodeView record is indicated by its signature, the first 32-bit value in the structure. For links to debugging information in contemporary usage, this is normally a <aclass="el"href="structcrashpad_1_1CodeViewRecordPDB70.html"title="A CodeView record linking to a .pdb 7.0 file. ">crashpad::CodeViewRecordPDB70</a> structure, but may be a <aclass="el"href="structcrashpad_1_1CodeViewRecordPDB20.html"title="A CodeView record linking to a .pdb 2.0 file. ">crashpad::CodeViewRecordPDB20</a> structure instead. These structures identify a link to debugging data within a <code>.pdb</code> (Program Database) file. See <ahref="http://www.debuginfo.com/articles/debuginfomatch.html#pdbfiles">Matching Debug Information</a>, PDB Files.</p>
<p>On Windows, it is also possible for the CodeView record to contain debugging information itself, as opposed to a link to a <code>.pdb</code> file. See <ahref="http://pierrelib.pagesperso-orange.fr/exec_formats/MS_Symbol_Type_v1.0.pdf#page=71">Microsoft Symbol and Type Information</a>, section 7.2, “Debug Information Format” for a list of debug information formats, and <ahref="http://undocumented.rawol.com/sbs-w2k-1-windows-2000-debugging-support.pdf#page=63">Undocumented Windows 2000 Secrets</a>, Windows 2000 Debugging Support/Microsoft Symbol File Internals/CodeView Subsections for an in-depth description of the CodeView 4.1 format. Signatures seen in the wild include “NB09” (0x3930424e) for CodeView 4.1 and “NB11” (0x3131424e) for CodeView 5.0. This form of debugging information within the module, as opposed to a link to an external <code>.pdb</code> file, is chosen by building with <code>/Z7</code> in Visual Studio 6.0 (1998) and earlier. This embedded form of debugging information is now considered obsolete.</p>
<p>On Windows, the CodeView record is taken from a module’s IMAGE_DEBUG_DIRECTORY entry whose Type field has the value IMAGE_DEBUG_TYPE_CODEVIEW (<code>2</code>), if any. Records in <aclass="el"href="structcrashpad_1_1CodeViewRecordPDB70.html"title="A CodeView record linking to a .pdb 7.0 file. ">crashpad::CodeViewRecordPDB70</a> format are generated by Visual Studio .NET (2002) (version 7.0) and later.</p>
<p>When the CodeView record is not present, the fields of this <aclass="el"href="structMINIDUMP__LOCATION__DESCRIPTOR.html"title="A pointer to a structure or union within a minidump file. ">MINIDUMP_LOCATION_DESCRIPTOR</a> will be <code>0</code>. </p>
<p>A pointer to the module’s miscellaneous debugging record, a structure of type <aclass="el"href="structIMAGE__DEBUG__MISC.html"title="Miscellaneous debugging record. ">IMAGE_DEBUG_MISC</a>. </p>
<p>This field is Windows-specific, and has no meaning on other operating systems. It is largely obsolete on Windows, where it was used to link to debugging information stored in a <code>.dbg</code> file. <code>.dbg</code> files have been superseded by <code>.pdb</code> files.</p>
<p>On Windows, the miscellaneous debugging record is taken from module’s IMAGE_DEBUG_DIRECTORY entry whose Type field has the value IMAGE_DEBUG_TYPE_MISC (<code>4</code>), if any.</p>
<p>When the miscellaneous debugging record is not present, the fields of this <aclass="el"href="structMINIDUMP__LOCATION__DESCRIPTOR.html"title="A pointer to a structure or union within a minidump file. ">MINIDUMP_LOCATION_DESCRIPTOR</a> will be <code>0</code>.</p>
<dlclass="section see"><dt>See also</dt><dd><aclass="el"href="structMINIDUMP__MODULE.html#acd07e35faf066880eeabea8a91aa887a"title="A pointer to the module’s CodeView record, typically a link to its debugging information in crashpad...">CvRecord</a></dd></dl>
<p>The module’s timestamp, in <code>time_t</code> units, seconds since the POSIX epoch, or <code>0</code> if unknown. </p>
<p>On Windows, this field comes from the <code>TimeDateStamp</code> field of the module’s <code>IMAGE_FILE_HEADER</code> structure. It reflects the timestamp at the time the module was linked. </p>
