Debug Windows crash dumps with an AI agent via MCP
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. Task: 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. We are currently running a private Beta test. If you are interested in debugging and want to ensure ForensicDbg surpasses your needs, request an invite. Advanced user-mode post-mortem debugger for Windows Debug x86 and x64 crash dumps Debug x86 and x64 crash dumps Attach to live processes Attach to live processes Set as just-in-time debugger to debug crashes when they happen Set as just-in-time debugger to debug crashes when they happen Simple C++ expression evaluator Simple C++ expression evaluator SourceServer and SourceLink support SourceServer and SourceLink support In active development with regular updates and feature additions In active development with regular updates and feature additions MCP interface for automated crash analysis with AI tools Interoperates with all AI tools that support stdio MCP Server communication Interoperates with all AI tools that support stdio MCP Server communication Output is tailored for efficient consumption by AI tools Output is tailored for efficient consumption by AI tools Higher quality data means better results from the AI Higher quality data means better results from the AI Interprets and labels data so the LLM doesn’t spend time doing it Interprets and labels data so the LLM doesn’t spend time doing it Reduces overall token costs while unlocking better results from your AI tools Reduces overall token costs while unlocking better results from your AI tools State-of-the-art UI built to be intuitive and responsive Color-coded output is understandable at a glance Color-coded output is understandable at a glance Navigate the process space by clicking on any address Navigate the process space by clicking on any address Memory regions are labeled with symbol names and object types Memory regions are labeled with symbol names and object types Objects displayed in structure initialization format Objects displayed in structure initialization format Multi-threaded symbol loading Multi-threaded symbol loading Panels are kept in-sync as you navigate Panels are kept in-sync as you navigate Light and dark modes that match your system Light and dark modes that match your system Data is interpreted using decades of expert experience Deduces types based on usage and references Deduces types based on usage and references Tracks register values as they flow through disassembly Tracks register values as they flow through disassembly Validates callstacks to remove misleading references Validates callstacks to remove misleading references Simulates image loader to reconstruct missing read-only regions in mini-dumps Simulates image loader to reconstruct missing read-only regions in mini-dumps Automatically selects the thread, frame, and instruction that caused the exception Automatically selects the thread, frame, and instruction that caused the exception ForensicDbg gives AI tools access to its powerful debugging engine through its MCP server, greatly improving the quality of results and significantly lowering the token cost of tracking down your hardest to catch bugs. We are currently running a private Beta test. If you are interested in debugging and want to ensure ForensicDbg surpasses your needs, request an invite. Bug CTextWindowBase::SetSelectionBegin doesn't null-check the CRefPtr<CTextLine> returned by GetLine() before dereferencing it to fetch m_link. This is only reachable when the window has no lines (GetLineCount() == 0) at the moment of a click — here, a disassembly panel that hasn't yet had a function/frame's code loaded into it (no region, no symbol walk, no frame selected). The fix is to guard the GetLine() result for null in SetSelectionBegin (CTextWindow.cpp around line 559) and skip the selection-link update when the window is empty. Advanced user-mode post-mortem debugger for Windows Debug x86 and x64 crash dumps Debug x86 and x64 crash dumps Attach to live processes Attach to live processes Set as just-in-time debugger to debug crashes when they happen Set as just-in-time debugger to debug crashes when they happen Simple C++ expression evaluator Simple C++ expression evaluator SourceServer and SourceLink support SourceServer and SourceLink support In active development with regular updates and feature additions In active development with regular updates and feature additions; tools: custom-built or unnamed agent. Human role: The original post does not say how a person stayed involved.; limitations: Requires access to the private Beta invite. Integration depends on AI tools supporting stdio MCP. Source reliability is secondary (vendor marketing). Human approval is mandatory for code changes. Token cost reduction is claimed but not quantified..
Tools
custom-built or unnamed agent
Published on Agent Work Atlas:
Overview
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.
Workflow
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. We are currently running a private Beta test. If you are interested in debugging and want to ensure ForensicDbg surpasses your needs, request an invite. Advanced user-mode post-mortem debugger for Windows Debug x86 and x64 crash dumps Debug x86 and x64 crash dumps Attach to live processes Attach to live processes Set as just-in-time debugger to debug crashes when they happen Set as just-in-time debugger to debug crashes when they happen Simple C++ expression evaluator Simple C++ expression evaluator SourceServer and SourceLink support SourceServer and SourceLink support In active development with regular updates and feature additions In active development with regular updates and feature additions MCP interface for automated crash analysis with AI tools Interoperates with all AI tools that support stdio MCP Server communication Interoperates with all AI tools that support stdio MCP Server communication Output is tailored for efficient consumption by AI tools Output is tailored for efficient consumption by AI tools Higher quality data means better results from the AI Higher quality data means better results from the AI Interprets and labels data so the LLM doesn’t spend time doing it Interprets and labels data so the LLM doesn’t spend time doing it Reduces overall token costs while unlocking better results from your AI tools Reduces overall token costs while unlocking better results from your AI tools State-of-the-art UI built to be intuitive and responsive Color-coded output is understandable at a glance Color-coded output is understandable at a glance Navigate the process space by clicking on any address Navigate the process space by clicking on any address Memory regions are labeled with symbol names and object types Memory regions are labeled with symbol names and object types Objects displayed in structure initialization format Objects displayed in structure initialization format Multi-threaded symbol loading Multi-threaded symbol loading Panels are kept in-sync as you navigate Panels are kept in-sync as you navigate Light and dark modes that match your system Light and dark modes that match your system Data is interpreted using decades of expert experience Deduces types based on usage and references Deduces types based on usage and references Tracks register values as they flow through disassembly Tracks register values as they flow through disassembly Validates callstacks to remove misleading references Validates callstacks to remove misleading references Simulates image loader to reconstruct missing read-only regions in mini-dumps Simulates image loader to reconstruct missing read-only regions in mini-dumps Automatically selects the thread, frame, and instruction that caused the exception Automatically selects the thread, frame, and instruction that caused the exception ForensicDbg gives AI tools access to its powerful debugging engine through its MCP server, greatly improving the quality of results and significantly lowering the token cost of tracking down your hardest to catch bugs. We are currently running a private Beta test. If you are interested in debugging and want to ensure ForensicDbg surpasses your needs, request an invite. Bug CTextWindowBase::SetSelectionBegin doesn't null-check the CRefPtr<CTextLine> returned by GetLine() before dereferencing it to fetch m_link. This is only reachable when the window has no lines (GetLineCount() == 0) at the moment of a click — here, a disassembly panel that hasn't yet had a function/frame's code loaded into it (no region, no symbol walk, no frame selected). The fix is to guard the GetLine() result for null in SetSelectionBegin (CTextWindow.cpp around line 559) and skip the selection-link update when the window is empty. Advanced user-mode post-mortem debugger for Windows Debug x86 and x64 crash dumps Debug x86 and x64 crash dumps Attach to live processes Attach to live processes Set as just-in-time debugger to debug crashes when they happen Set as just-in-time debugger to debug crashes when they happen Simple C++ expression evaluator Simple C++ expression evaluator SourceServer and SourceLink support SourceServer and SourceLink support In active development with regular updates and feature additions In active development with regular updates and feature additions
Reported result
No measured outcomes are reported in the source. The tool is in private Beta. A proposed acceptance check is to verify that the AI correctly identifies the null-pointer dereference in CTextWindowBase::SetSelectionBegin from a provided dump, matching the documented bug example.
Human role
The original post does not say how a person stayed involved.
Limitations
Requires access to the private Beta invite. Integration depends on AI tools supporting stdio MCP. Source reliability is secondary (vendor marketing). Human approval is mandatory for code changes. Token cost reduction is claimed but not quantified.
Try it
I need to debug a Windows crash dump using ForensicDbg and an AI agent. [replaceable: path to .dmp file]. [replaceable: source code repository URL]. Configure ForensicDbg as an MCP server. Connect your AI agent to this server. Query the debugger for the exception thread, callstack, and relevant memory regions. Analyze the structured output to identify the root cause. Propose a specific code fix with file and line numbers. Do not apply changes. Output a report: 1. Root Cause Analysis, 2. Proposed Fix, 3. Confidence Level. Wait for my confirmation before proceeding. If the dump is unreadable, report the error immediately.
Source reports are not independently verified. Publication date is the catalog publication date, not the original article date.