ForensicDbg - Advanced post-mortem debugger for Windows x64/x86 crashes

Show HN: I built a post-mortem debugger for native Windows x64/x86 crashes

ForensicDbg is a modern post-mortem debugger built from the ground up to help you quickly track down and fix your hardest-to-catch bugs. It supports debugging x86 and x64 crash dumps, attaching to live processes, and acting as a just-in-time debugger. With a simple C++ expression evaluator, SourceServer and SourceLink support, and an MCP interface for AI-powered crash analysis, it streamlines your debugging workflow. The intuitive UI features color-coded output, clickable addresses, and multi-threaded symbol loading. Currently in private beta, request an invite to experience its state-of-the-art capabilities.

ForensicDbg is a modern post-mortem debugger, designed from the ground-up to let you quickly and easily track down and identify your hardest to catch bugs.
  1. neitsa

    While I really do appreciate having multiple choices when it comes to tooling I beg to differ when saying that windbg is archaic. As someone who is spending a lot of time with windbg, I think it's fair to say they really put some effort in it: TTD (time travel debugging), JS scriping, Linux core dump support, new type of queries and the data model, new commands, and an upcoming integrated MCP (functionalities \ function names visible in the data model). That being said, there's a lot of baggage for such an old software and there are definitely some pain points.

    But as said, I like to have a choice (I sometimes use x64dbg for example), so the more, the merrier!

    I'll definitely give yours a try. Good luck for the beta and the release!

  2. _dky

    Reminds of CANASTA for VMS operating system. I never used it but heard many war stories where developers and support would analyze complex crashes in cluster software.

    https://cdn.aaai.org/IAAI/1991/IAAI91-013.pdf

  3. kjksf

    consider this a constructive criticism: improve the landing page.

    The video is a good idea but not like this. It's both large and I can't see anything, just things moving.

    When I fullscreen, instead of getting larger video, I get the same thing.

    Record a video (and upload to youtube) that does a well-paced walkthrough of doing an analysis, with narration, maybe demonstrating how it's unique / different from windbg.

More from this day

2026-09-23