Crash Dump Analyzer
Upload a Windows minidump (.dmp) or Linux core file to extract readable structural info, entirely in your browser.
How to use this tool
Choose a .dmp (Windows minidump) or Linux core file — the format is auto-detected and parsed immediately. Nothing is uploaded.
About this tool
Extracts structural information directly stored in the dump file: for Windows minidumps, system info (OS version, CPU architecture) and the loaded module list (name, base address, size); for Linux core files, the process name/command line, PID, and thread info from the file's ELF notes (NT_PRPSINFO, NT_PRSTATUS).
This does not resolve addresses to function names (symbolication) — that requires matching debug symbols this tool has no access to. It reports the raw, directly-available structural data only.
100% client-side, using the browser's File API. Your dump file is never uploaded.
Frequently asked questions
Does this resolve function names in the stack trace?
No. Resolving addresses to function/file/line names (symbolication) requires the matching debug symbols (a .pdb file for Windows, or DWARF debug info for Linux) for the exact build that crashed. This tool only extracts what's directly stored in the dump file itself: process info, loaded module list with base addresses, thread IDs, and raw register values.
Is my crash dump file uploaded anywhere?
No. The file is read and parsed entirely in your browser using the File API. It is never uploaded to a server, which matters since crash dumps can contain sensitive memory contents.
How was this parser verified?
The Linux ELF core parser was verified against a hand-built test file cross-checked with the standard readelf tool. The Windows minidump parser follows the publicly documented Microsoft structure layout, verified via round-trip construction/parsing tests, but has not been tested against a real Windows-generated dump file. Report unexpected results using the site's contact.