如需損毀傾印檔案的簡介和概觀，請參閱損 毀傾印檔案。
開啟傾印檔案
To open a crash dump file for use as a debugger target, use OpenDumpFile or OpenDumpfileWide. These methods are similar to the .opendump debugger command.
Note The engine doesn't completely attach to the dump file until the WaitForEvent method has been called. 從進程或核心建立傾印檔案時，最後一個事件的相關信息會儲存在傾印檔案中。 開啟傾印檔案之後，下次嘗試執行時，引擎就會針對事件回呼產生這個事件。 只有這樣，傾印檔案才會在偵錯會話中使用。 如需詳細資訊，請參閱 偵錯會話和執行模型 。
其他檔案可用來協助偵錯損毀傾印檔案。 The methods AddDumpInformationFile and AddDumpInformationFileWide register files containing page-file information to be used when the next dump file is opened. 必須在開啟傾印檔案之前呼叫這些方法。 GetNumberDumpFiles will return the number of such files that were used when the current dump file was opened and GetDumpFile will return a description of these files.
使用者模式小型傾印檔案包含數個資訊資料流程。 These streams can be read using the Request operation DEBUG_REQUEST_READ_USER_MINIDUMP_STREAM.
建立傾印檔案
To create a crash dump file of the current target -- user-mode or kernel-mode -- use WriteDumpFile2. This method is similar to the .dump debugger command.