WinDbg Web

A browser-based, WinDbg-styled viewer for Windows crash dump (.dmp) files. It is not the real Microsoft debugger — it is an independent tool that parses the dump binary format directly in your browser and reproduces a subset of WinDbg's command output from the data structurally present in the file. The dump file itself is never uploaded anywhere; the only outbound requests this app makes are tiny module identifiers (a PDB filename + GUID/age, see Symbols below) sent to fetch public symbols.

Two formats are supported: user-mode minidumps ("MDMP", from app crashes/Task Manager/WER) — loaded modules, threads, register context, exception record, captured memory ranges; and kernel/full BSOD dumps ("PAGEDUMP"/"PAGEDU64") — bugcheck code/arguments and the faulting processor's registers always come straight from the header, while the driver list and stack walk additionally require this dump to be a "Full" dump (so its physical memory is present to translate virtual addresses via page tables).

Stack traces beyond the topmost frame are a best-effort reconstruction (frame-pointer chain on x86, heuristic stack scan on x64) since full unwinding requires PDBs/unwind metadata that dumps don't contain. Disassembly and type dumping are still unavailable, since dump files never carry code bytes or type info.

Symbols are handled two ways. When a module carries a CodeView (RSDS/PDB) record -- true for anything Microsoft shipped -- this app automatically downloads its public symbols from Microsoft's symbol server as soon as the dump loads, via a small same-origin proxy on this server (the browser can't reach msdl.microsoft.com directly -- it sends no CORS headers) and a PDB parser that runs entirely in your browser. Re-trigger it any time with .symfetch <module>.

For anything that isn't a Microsoft binary (your own app.exe, a third-party DLL) the public symbol server has nothing, which is expected -- use .symload <module> (or File > Load Symbols for Module…) to load your own symbols from a local file instead (an MSVC linker .map file, plain nm-style "address name" lines, or JSON), read entirely client-side.

Either way, once a module has symbols loaded, addresses inside it resolve to module!function+0xoffset in k, r, !analyze, x and ln instead of just module+0xoffset.