Information for one module as recorded during execution.
The checksum field as stored in the module headers.
The unique index of the module segment for the base address of the containing module. If the module consists of a single contiguous mapping (the typical case), there is only one index for the whole module. If the module has gaps in its mapping, each non-contiguous segment has its own index, with this field pointing to the index of the segment with the lowest base address.
The custom field set by the
load_cb passed to drmodtrack_add_custom_data().
The unique index of this module segment. This equals the
index parameter passed to drmodtrack_offline_lookup().
The offset of this segment from the beginning of this backing file. If this field is not present in an older-version offline file, it will be filled in with -1. On Windows this field is always 0.
The full path to the file backing the module. This points to a buffer of size MAXIMUM_PATH. It can be modified.
The preferred base address of this segment of the module. If this field is not present in an older-version offline file, it will be filled in with -1.
The size of this segment of the module.
The start address of this segment of the module as it was during execution. If the module has multiple non-contiguous segments, each segment will have a distinct entry with its own unique index identifier. The
containing_index field can be used to identify which segments belong to the same module. They will also all have the same
Used for compatibility purposes for adding new fields, the user must set this value to the size of the structure.
The timestamp field as stored in the module headers.
The documentation for this struct was generated from the following file: