Identifies the type of information that will be written to the minidump file by the MiniDumpWriteDump function.

Syntax

typedef enum _MINIDUMP_TYPE {
  MiniDumpNormal                           = 0x00000000,
  MiniDumpWithDataSegs                     = 0x00000001,
  MiniDumpWithFullMemory                   = 0x00000002,
  MiniDumpWithHandleData                   = 0x00000004,
  MiniDumpFilterMemory                     = 0x00000008,
  MiniDumpScanMemory                       = 0x00000010,
  MiniDumpWithUnloadedModules              = 0x00000020,
  MiniDumpWithIndirectlyReferencedMemory   = 0x00000040,
  MiniDumpFilterModulePaths                = 0x00000080,
  MiniDumpWithProcessThreadData            = 0x00000100,
  MiniDumpWithPrivateReadWriteMemory       = 0x00000200,
  MiniDumpWithoutOptionalData              = 0x00000400,
  MiniDumpWithFullMemoryInfo               = 0x00000800,
  MiniDumpWithThreadInfo                   = 0x00001000,
  MiniDumpWithCodeSegs                     = 0x00002000,
  MiniDumpWithoutAuxiliaryState            = 0x00004000,
  MiniDumpWithFullAuxiliaryState           = 0x00008000,
  MiniDumpWithPrivateWriteCopyMemory       = 0x00010000,
  MiniDumpIgnoreInaccessibleMemory         = 0x00020000,
  MiniDumpWithTokenInformation             = 0x00040000 
} MINIDUMP_TYPE;

Constants

MiniDumpNormal

Include just the information necessary to capture stack traces for all existing threads in a process.

MiniDumpWithDataSegs

Include the data sections from all loaded modules. This results in the inclusion of global variables, which can make the minidump file significantly larger. For per-module control, use the ModuleWriteDataSeg enumeration value from MODULE_WRITE_FLAGS.

MiniDumpWithFullMemory

Include all accessible memory in the process. The raw memory data is included at the end, so that the initial structures can be mapped directly without the raw memory information. This option can result in a very large file.

MiniDumpWithHandleData

Include high-level information about the operating system handles that are active when the minidump is made.

MiniDumpFilterMemory

Stack and backing store memory written to the minidump file should be filtered to remove all but the pointer values necessary to reconstruct a stack trace. Typically, this removes any private information.

MiniDumpScanMemory

Stack and backing store memory should be scanned for pointer references to modules in the module list. If a module is referenced by stack or backing store memory, the ModuleWriteFlags member of the MINIDUMP_CALLBACK_OUTPUT structure is set to ModuleReferencedByMemory.

MiniDumpWithUnloadedModules

Include information from the list of modules that were recently unloaded, if this information is maintained by the operating system.

Windows Server 2003 and Windows XP:  The operating system does not maintain information for unloaded modules until Windows Server 2003 with SP1 and Windows XP with SP2.

DbgHelp 5.1:  This value is not supported.

MiniDumpWithIndirectlyReferencedMemory

Include pages with data referenced by locals or other stack memory. This option can increase the size of the minidump file significantly.

DbgHelp 5.1:  This value is not supported.

MiniDumpFilterModulePaths

Filter module paths for information such as user names or important directories. This option may prevent the system from locating the image file and should be used only in special situations.

DbgHelp 5.1:  This value is not supported.

MiniDumpWithProcessThreadData

Include complete per-process and per-thread information from the operating system.

DbgHelp 5.1:  This value is not supported.

MiniDumpWithPrivateReadWriteMemory

Scan the virtual address space for PAGE_READWRITE memory to be included.

DbgHelp 5.1:  This value is not supported.

MiniDumpWithoutOptionalData

Reduce the data that is dumped by eliminating memory regions that are not essential to meet criteria specified for the dump. This can avoid dumping memory that may contain data that is private to the user. However, it is not a guarantee that no private information will be present.

DbgHelp 6.1 and earlier:  This value is not supported.

MiniDumpWithFullMemoryInfo

Include memory region information. For more information, see MINIDUMP_MEMORY_INFO_LIST.

DbgHelp 6.1 and earlier:  This value is not supported.

MiniDumpWithThreadInfo

Include thread state information. For more information, see MINIDUMP_THREAD_INFO_LIST.

DbgHelp 6.1 and earlier:  This value is not supported.

MiniDumpWithCodeSegs

Include all code and code-related sections from loaded modules to capture executable content. For per-module control, use the ModuleWriteCodeSegs enumeration value from MODULE_WRITE_FLAGS.

DbgHelp 6.1 and earlier:  This value is not supported.

MiniDumpWithoutAuxiliaryState

Turns off secondary auxiliary-supported memory gathering.

MiniDumpWithFullAuxiliaryState

Requests that auxiliary data providers include their state in the dump image; the state data that is included is provider dependent. This option can result in a large dump image.

MiniDumpWithPrivateWriteCopyMemory

Scans the virtual address space for PAGE_WRITECOPY memory to be included.

Prior to DbgHelp 6.1:  This value is not supported.

MiniDumpIgnoreInaccessibleMemory

If you specify MiniDumpWithFullMemory, the MiniDumpWriteDump function will fail if the function cannot read the memory regions; however, if you include MiniDumpIgnoreInaccessibleMemory, the MiniDumpWriteDump function will ignore the memory read failures and continue to generate the dump. Note that the inaccessible memory regions are not included in the dump.

Prior to DbgHelp 6.1:  This value is not supported.

MiniDumpWithTokenInformation

Adds security token related data. This will make the "!token" extension work when processing a user-mode dump.

Prior to DbgHelp 6.1:  This value is not supported.

Requirements

See Also

MiniDumpWriteDump

Send comments about this topic to Microsoft

Build date: 11/12/2009