rr-debugger

Record and replay native binaries with rr for deterministic reverse debugging.

482|72|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/deonmenezes/mantishack --skill rr-debugger-deonmenezes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rr-debugger
Source: https://github.com/deonmenezes/mantishack/tree/main/.claude/skills/crash-analysis/rr-debugger
Command: npx skills add https://github.com/deonmenezes/mantishack --skill rr-debugger-deonmenezes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

rr-based deterministic reverse debugging for crashes and ASAN faults using rr record-replay, enabling precise replay and retrospective analysis.

Core Features & Use Cases

  • Deterministic reverse execution: step back through program execution to identify root causes.
  • Reverse commands: reverse-next, reverse-step, reverse-continue, and reverse-instruction stepping for efficient fault localization.
  • Crash trace extraction: capture and inspect traces to understand failure paths.
  • Use Case: debugging a binary crash in a complex workflow by replaying the exact sequence leading to the fault.

Quick Start

Record a program with rr and then use rr replay to step backward and investigate crashes.

Frequently Asked Questions about rr-debugger

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug a native binary crash by stepping backward through execution?

Reverse debugging a native binary crash is achieved by recording the program with rr and using rr replay to step backward, extracting the crash trace to investigate the exact sequence leading to the fault.

Can I debug AddressSanitizer faults using deterministic record-replay?

AddressSanitizer faults can be debugged deterministically using rr record-replay, which captures the exact execution state to enable reverse execution and precise retrospective analysis of ASAN failures.

What gdb reverse commands are available for crash trace extraction?

Reverse debugging supports gdb reverse commands including reverse-next, reverse-step, reverse-continue, and reverse-instruction stepping to navigate backward through program execution for efficient fault localization.

Do I need rr installed to replay a recorded program execution?

Yes, rr must be installed to record and replay a target program, providing the deterministic record-replay environment required for reverse execution and crash trace extraction.

What is the best way to debug a complex workflow binary crash deterministically?

Deterministic reverse debugging is the best way to analyze a binary crash in a complex workflow, replaying the exact recorded sequence to step back and identify the root cause of the failure.

Why use deterministic reverse execution instead of standard forward debugging for crash analysis?

Deterministic reverse execution allows you to step back through the exact program sequence leading to a crash, whereas standard forward debugging often fails to reproduce intermittent faults and trace the exact failure path.