ForensicDbg

Modern post-mortem debugger for your hardest-to-catch bugs

debugger

post-mortem debugging

crash analysis

windows

ai debugging

mcp

ForensicDbg is a modern post-mortem debugger for Windows designed to help developers quickly track down and identify hard-to-catch bugs. It supports debugging x86 and x64 crash dumps, attaching to live processes, and acting as a just-in-time debugger. It also exposes an MCP interface that lets AI tools perform automated crash analysis with lower token costs and higher-quality results. The product is currently in a private beta test with invite requests open, and is in active development with regular updates.

Key Features

Post-mortem and live debugging

Debug x86 and x64 crash dumps, attach to live processes, and set ForensicDbg as a just-in-time debugger to catch crashes as they happen.

C++ expression evaluation and source indexing

Includes a simple C++ expression evaluator plus SourceServer and SourceLink support.

AI debugging via MCP

An MCP server interface interoperates with all AI tools that support stdio MCP communication; output is tailored for efficient AI consumption, data is pre-interpreted and labeled, reducing token costs while improving results.

Smart crash analysis

Deduces types from usage and references, tracks register values through disassembly, validates callstacks to remove misleading references, and automatically selects the thread, frame, and instruction that caused the exception.

Mini-dump reconstruction

Simulates the image loader to reconstruct missing read-only regions in mini-dumps.

Modern debugging UI

Color-coded output, click-to-navigate process space, memory regions labeled with symbol names and object types, structure-initialization object display, multi-threaded symbol loading, synchronized panels, and light/dark modes.

How It Works

1
Debug crashes locally or post-mortem
Open x86/x64 crash dumps, attach to live processes, or register as the just-in-time debugger so crashes can be inspected the moment they occur.
2
Let the engine interpret the data
ForensicDbg deduces types, tracks register values through disassembly, validates callstacks, and simulates the image loader to fill gaps in mini-dumps, automatically landing on the exception-causing thread, frame, and instruction.
3
Integrate with AI tools via MCP
Connect AI tools that support stdio MCP servers to ForensicDbg's debugging engine; pre-labeled, structured output gives the LLM higher-quality data at lower token cost for automated crash analysis.

Pros & Cons

Pros

Handles crash dumps, live process attachment, and just-in-time debugging in one tool
MCP server makes crash analysis automatable with any stdio-compatible AI tool
Pre-interprets and labels data, which lowers AI token costs and improves analysis quality
Smart analysis features such as callstack validation, register tracking, and automatic exception-location selection
Modern, responsive UI with color-coded output, clickable address navigation, and synced panels
SourceServer and SourceLink support plus a C++ expression evaluator

Cons

Windows-only (user-mode debugger for x86 and x64); no support for other operating systems mentioned
User-mode only — no kernel-mode debugging is mentioned
Currently in private beta, so access requires an invite
C++ expression evaluator is described as simple, suggesting limited expression support
In active development, so feature set is still growing and may change

Who It's For

Best for

Windows C/C++ developers tracking down hard-to-catch crashes and bugs
Teams that want to automate crash triage with AI tools over MCP
Engineers analyzing crash dumps and mini-dumps where data is incomplete or misleading
Developers who want a modern, responsive alternative UI for post-mortem debugging

Not ideal for

Developers debugging on macOS or Linux
Kernel-mode or driver debugging work
Non-Windows binaries or non-x86/x64 architectures
Users who need a fully released, stable product right now (it is in private beta)

Use Cases

Diagnosing hard-to-reproduce crashes from x86/x64 crash dumps on Windows
Debugging live processes and catching crashes via just-in-time debugging
Automating crash triage by connecting AI tools through the MCP interface
Analyzing mini-dumps with missing read-only regions via image loader simulation

FAQ

What is ForensicDbg?

ForensicDbg is a modern post-mortem debugger for Windows designed to help you quickly track down and identify your hardest-to-catch bugs, with both a visual debugging UI and AI debugging via an MCP interface.

What platforms does it run on?

It is an advanced user-mode post-mortem debugger for Windows, supporting both x86 and x64 crash dumps.

Can it debug live processes or only crash dumps?

It supports debugging x86 and x64 crash dumps, attaching to live processes, and being set as the just-in-time debugger to catch crashes when they happen.

How does the AI integration work?

ForensicDbg exposes its debugging engine through an MCP server. It interoperates with any AI tool that supports stdio MCP server communication, with output tailored for efficient AI consumption so the LLM spends less time interpreting data and fewer tokens overall.

Is ForensicDbg free?

ForensicDbg is currently running a private beta test, and interested users can request an invite. Pricing for the released product is not stated on the site.

Is ForensicDbg open source?

The site does not indicate that ForensicDbg is open source; it appears to be a proprietary tool with a Releases page for updates.

How mature is the product?

It is in active development with regular updates and feature additions, and is currently in a private beta phase.