ForensicDbg announced a private beta of its Windows‑only post‑mortem debugger, supporting both x86 and x64 crash dumps and a just‑in‑time (JIT) debugger that can attach when a process crashes. The beta is invitation‑only and promises a modern UI, source‑server integration, and an MCP interface for AI‑driven analysis.
Core capabilities
The tool can open native crash dumps, attach to live processes, and be set as the system JIT debugger. It includes a simple C++ expression evaluator, SourceServer/SourceLink support, and multi‑threaded symbol loading. The UI offers dark and light modes, color‑coded disassembly, and clickable addresses that keep panels in sync.
AI‑friendly output
ForensicDbg ships an MCP server that streams structured debugging data to any AI tool that reads from stdio. By interpreting registers, validating call stacks, and labeling memory regions, it reduces the amount of raw token data an LLM must process, which can lower token costs and improve answer quality. The output format is designed for efficient consumption by downstream AI pipelines.
Caveats and trade‑offs
The beta is still in active development, so expect occasional UI glitches and incomplete feature parity with mature debuggers like WinDbg. Because the MCP interface is proprietary to ForensicDbg, integrating it ties you to their data format, which could complicate future tool switches. Additionally, while the AI output reduces token usage, the extra preprocessing step adds latency that may not matter for occasional crash analysis but could affect tight CI loops.
When to give it a try
If you regularly debug native Windows crashes and want a UI that surfaces richer context for AI‑assisted triage, request an invite and run it alongside your existing toolchain. Keep an eye on the public release roadmap; early adopters will get the first look at feature expansions such as automated crash‑analysis scripts.
What to watch: the transition from private beta to an open beta or GA release, and any community‑contributed MCP adapters that broaden AI tool compatibility.