View Image

CrashDump Extractor can process crash dump files to reveal information concerning the cause of the crash, which is ultimately the first step towards finding a solution for the problem. To put it another way, this application can help software authors transform raw crash dump files received from software users into bugs that need fixing. CrashDump Extractor makes use of the Windows debugger to extract information stored in dump files generated by the operating system when an application crashes. Developers can then detect the bug and its causes, and try to find fixes. To avoid unintended data loss, users should remember that deleting a dump file from the program will also erase the data from the disk.

In Windows development, when an application crashes, it often generates what is called a "crash dump". This file contains all the information regarding the last instruction executed by the software that led to the crash. It contains also all the context (understand memory) at the moment of the crash. That information is gold for the developer because it's most of the time more than enough to fix the issue. If you have setup a policy to collect those crash dumps (upload form at restart) you now have a whole folder full of crash dumps waiting for analysis.

Here comes Adlice CDE. Give it a folder to analyse, configure the symbols server path and it will show you everything categorized by bug. You won't need to analyze dozens of crash dumps telling the same story, just one of each. CDE uses one monitor per software and watches a folder for new dumps. This can be used with a cloud (Dropbox, Drive) to synchronize new crash dumps on a dev machine.