Reading a windows *.dmp file

Reading a windows *.dmp file

I was wonder if any knows how to open up a windows *.dmp file after a application crash written C/C++.

Windows threading: _beginthread vs _beginthreadex vs CreateThread C++


How can I enforce a maximum amount of forked children?
Using Visual Studio's File>Open Project or the free WinDbg's (part of Debugging Tools for Windows) File>Open Crash Dump select the dmp file..
What does a const pointer-to-pointer mean in C and in C++?
Make sure to configure the tools to include a path to the location of the PDB debugging symbols for that application (you do have symbols right?).

How loader Maps DLL in to Process Address Space
Either tool has a thread and call stack window that should give you a good idea where the crash occurred.

How to find out if a pointer is on the stack on PC/Visual C++
Including paths to the source code will help as well..
Looking for OSS for OSI Layer 2 Traffic Generator [closed]
Symbol and Source paths can be set in WinDbg under the File menu.

How do C/C++ compilers handle type casting between types with different value ranges?
It's buried in Visual Studio under Tools>Options>Debugging>Symbols and Tools>Options>Project and Solutions>VC++ Directores.
Viewing language (C/C++) reference/documentation in CodeBlocks


Here's a link to an article from Microsoft on reading the small memory dump files that Windows creates for debugging.


When using Debugging Tools for Windows be sure to setup symbols.

For Microsoft symbols use: SRV*DownstreamStore* For example: SRV*c:\websymbols* Take a look at these blogs for more on debugging:.


If you mean a dump file created by windows (either small memory dump, kernel memory dump or full memory dump) that is created after a system crash then you need WinDBG.


You should be able to just double click the .dmp file to automatically open it in Visual Studio.

If the .pdb file that was generated when the program was compiled is still around, Visual Studio should be able to automatically load the symbols from that.

From then on, you can just hit Run/Debug (F5) to start peeking into the .dmp file..

98 out of 100 based on 88 user ratings 1238 reviews