F FaultDebug
OPEN SOURCE · LOCAL FIRST · CLI + MCP

Follow a failure
to its evidence.

Turn C/C++ crashes into source-verified execution-flow reports. Follow recorded calls across services, inspect the fault location, and see what evidence is missing.

No account. No installation.Recorded synthetic runs, not a live monitor.
checkout → payment · SIGILLOpen report ↗
Recorded shopping-service payment crash with source evidence
TRY THE REPORTS

One checkout. Three outcomes.

Choose a case, then select a service or RPC to inspect its evidence.

01 / HTTP 200

Successful checkout

Follow the recorded reservation, payment, shipping and notification calls.

Follow the happy path →
02 / SIGILL → HTTP 502

Payment process crashes

See the missing receiver end, caller failure and native crash linked to verified source.

Find the crash evidence →
03 / HTTP 504

Inventory times out

Compare caller timeout and receiver observations without treating the injection setting as proof.

Inspect the timeout →

Also explore a real native C SIGSEGV capture → · Download native evidence

SEE IT IN ACTION

From failed request to source.

A short walkthrough of the actual interactive report: service flow, selected RPC, and source-verified native crash.

RUN THE REAL FIXTURE

Try it on your machine.

Linux x86_64 + local Docker Engine and Compose. The script downloads a checksummed prebuilt image, runs 8 services and opens a local report server. No host Python, Clang or CMake installation.

git clone https://github.com/lsh235/FaultDebugMCP.git
cd FaultDebugMCP
./scripts/try-demo.sh

The runner uses your local Docker socket to create and remove its own fixture containers. Ctrl+C stops the report server. Existing output directories are never overwritten.

CHECK THE EVIDENCE

Useful findings. Visible limits.

The shopping app is Python with an instrumented C++ boundary. These are native boundary events, not Python stacks. A stable snapshot can still be incomplete; the payment crash keeps that limitation visible.

8independent service processes
3recorded scenarios
LocalCLI + read-only MCP inspection

Make failures easier to explain.

Try a report, tell us what was unclear, or contribute a small improvement. If FaultDebug is useful to you, star the repository to follow its progress.