CrashDumpExtractor (CDE) is a tool able to parse crash dumps on demand (or from a monitored folder), display information and stack trace (from given symbols) and keep them in a database.
|File Size||1.35 MB|
|Operating System||Windows XP, Vista, 7, 8, 8.1, 10. 32/64 bits|
|Tags||crash dump debugging development manager|
CDE can be used to monitor a folder that you setup to receive (automatically or not) crash dumps from your applications (like from Dropbox).
CDE will extract information from those dumps, classify them by "Bucket ID" (this is a way to identify a bug) and display them in the interface. All you need it to open them, work on them and delete them. Warning: If you delete a dump from the program, it will be deleted on disk as well.
- Parse crash dumps in either compressed (gz only) format or raw format.
- Extract Program name, Program version and stack trace (given symbols).
- Monitor a folder for new dumps. They are automatically parsed/added when they arrive.
- Display dumps in a "Bucket Id" organized view, by Id (unique string identifying a crash/exception).
- Open a crash dump for analysis (with default program, can be Visual Studio, WindDBG).
- Open the program. Configure CDB path, as well as symbols and sources path. Typically, CDB path is C:/Program Files (x86)/Windows Kits/8.1/Debuggers/x64/cdb.exe, check and adapt to your machine.
- You can setup monitored folder path and activation (optional).
- Use the button to open a crash dump, or drop it in the interface.
- If monitoring is enabled, every new file is parsed and added to the database.
- When you double click on a bucket, it will be opened. You can then see all the dumps inside that bucket. A bucket regroups several crash dumps occurring for the same reason (probably the same bug). When you double click on a dump, you can see the full call stack, as well as full CDB output.