Although you cannot continue execution, you can examine the stacks, threads, and variable values of the app at the time the dump occurred.ĭebugging dump files of optimized code can be confusing. Opening a dump file with a heap in Visual Studio is like stopping at a breakpoint in a debug session. If the dump was saved with heap information, the dump file contains a snapshot of what was in the app’s memory at that point in time. It shows what process was executing and what modules were loaded. If you have a Microsoft debugger and the symbols for the relevant progams, then you can have a look at the dump file yourself:Ī dump file is a snapshot of an app at the point in time the dump is taken.
HDMP file and can be sent to Microsoft as part of a bug reporting process. *.mdmp files are considered to be Microsoft Dump Files.Ĭompressed file created by Windows after a program error or crash contains data “dumped” from the program’s memory space saves information about the error, which can be used for debugging commonly created along with an uncompressed. You might want to consider opening an issue on MongoDB’s Issue Tracker and providing the *.mdmp file in the issue.
0 kommentar(er)
