.opendump (Open Dump File)
The .opendump command opens a dump file for debugging.
.opendump DumpFile
.opendump /c "DumpFileInArchive" [CabFile]
Parameters
DumpFile
Specifies the name of the dump file to open. DumpFile should include the file name extension (typically .dmp or .mdmp) and can include an absolute or relative path. Relative paths are relative to the directory that you started the debugger in.
/c "DumpFileInArchive"
Specifies the name of a dump file to debug. This dump file must be contained in the archive file that CabFile specifies. You must enclose the DumpFileInArchive file in quotation marks.
CabFile
Specifies the name of an archive file to open. CabFileshould include the file name extension (typically .cab) and can include an absolute or relative path. Relative paths are relative to the directory that you started the debugger in. If you use the /c switch to specify a dump file in an archive but you omit CabFile, the debugger reuses the archive file that you most recently opened.
Environment
Modes |
User mode, kernel mode |
Targets |
Crash dump only (but you can use this command if other sessions are running) |
Platforms |
All |
Remarks
After you use the .opendump command, you must use the g (Go) command to finish loading the dump file.
When you are opening an archive file (such as a CAB file), you should use the /c switch. If you do not use this switch and you specify an archive for DumpFile, the debugger opens the first file that has an .mdmp or .dmp file name extension within this archive.
You can use .opendump even if a debugging session is already in progress. This feature enables you to debug more than one crash dump at the same time. For more information about how to control a multiple-target session, see Debugging Multiple Targets.
Note There are complications, when you debug live targets and dump targets together, because commands behave differently for each type of debugging. For example, if you use the g (Go) command when the current system is a dump file, the debugger begins executing, but you cannot break back into the debugger, because the break command is not recognized as valid for dump file debugging.