Developer Releases ForensicDbg, a Post-Mortem Debugger for Native Windows x64/x86 Crashes
A developer has released ForensicDbg, a post-mortem debugger for native Windows x64 and x86 crashes, in a Show HN post that positions it between Visual Studio and WinDbg and includes an MCP server for agentic debugging.
According to the post, the project grew out of years spent debugging Windows crashes with tools the developer characterizes as either friendly but limited, naming Visual Studio, or powerful but archaic, naming WinDbg. The patterns and methods developed while working through those crashes were built into the new tool rather than applied by hand.
ForensicDbg presents what the developer calls a modern interface meant to reduce friction during debugging. All data shown to the user is analyzed, interpreted and presented plainly, and the elements are interlinked so that a user can navigate the process space quickly, the post states. The tool is aimed at post-mortem analysis, working from data left by a crash rather than from a live debugging session.
The release also includes an MCP server, which the developer says allows for agentic debugging. The same interpretation and interlinking work done for the human interface is intended to give AI tools a stable foundation to operate from, which the developer says removes the risk of hallucinations and avoids spending tokens, referring to the cost of model queries.
The developer is distributing the tool through a free beta license obtained by signing up at forensicdbg.com/beta. The submission listed three points and no comments on Hacker News at the time of the post, and the post did not state pricing for any eventual commercial version or a release date beyond the beta.
The post did not name the developer or provide a company affiliation, and no benchmarks, supported Windows versions or comparison figures against Visual Studio and WinDbg were included. The description of the tool's advantages and of its effect on AI-generated debugging output comes from the developer's own account of the project, and no third-party testing or review was cited.