rr-debugger

Records and replays program execution to diagnose faults with rr-compatible tools.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/dawsonblock/OracleOS --skill rr-debugger-dawsonblock
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rr-debugger
Source: https://github.com/dawsonblock/OracleOS/tree/main/Interface/Web/raptor-main/.claude/skills/crash-analysis/rr-debugger
Command: npx skills add https://github.com/dawsonblock/OracleOS --skill rr-debugger-dawsonblock

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Deterministic reverse-debugging of crashes and ASAN faults via rr record-replay, enabling precise replay and trace extraction to diagnose failures.

Core Features & Use Cases

  • Deterministic reverse-debugging: reverse-next, reverse-step, reverse-continue for pinpointing faults.
  • Crash trace extraction and memory/variable inspection during replay.
  • Automated trace extraction through a script to streamline debugging workflows.

Quick Start

Run rr record <program> to capture execution, then rr replay and use reverse commands to locate the fault.

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 crash by replaying program execution in reverse?

Reverse-debugging a crash involves recording program execution with rr and replaying it in gdb to step backwards. This deterministic record-replay approach lets you reverse-next, reverse-step, and reverse-continue to pinpoint the exact fault.

Can I use gdb to debug ASAN faults deterministically?

Yes, you can debug ASAN faults deterministically by recording the faulting execution with rr and replaying it in gdb. This allows precise memory and variable inspection during replay to locate the source of the ASAN fault.

What is the best way to extract a crash trace from a replayed recording?

The best way to extract a crash trace is to use an automation script during the rr replay session. This script streamlines the debugging workflow by automatically extracting the trace from the recorded crash scenario.

Does rr reverse-execution support pinpointing the root cause of intermittent crashes?

rr reverse-execution supports pinpointing the root cause of intermittent crashes by providing deterministic record-replay. This eliminates non-determinism, allowing you to reliably reproduce the crash and step backwards to the origin.

Do I need rr and gdb installed to run deterministic reverse-debugging?

Yes, you need both rr and gdb installed to run deterministic reverse-debugging. rr handles the recording and replay of the program execution, while gdb provides the interface for reverse execution and variable inspection.