Record and replay native application crashes with rr reverse-execution debugging.
npx skills add https://github.com/gadievron/raptor --skill rr-debugger
Please help me install this Agent Skill. Skill: rr-debugger Source: https://github.com/gadievron/raptor/tree/main/.claude/skills/crash-analysis/rr-debugger Command: npx skills add https://github.com/gadievron/raptor --skill rr-debugger
This Skill enables deterministic debugging of crashes and ASAN faults by using rr's record-replay capabilities and reverse execution to observe, step back, and trace the sequence leading to failures.
Use rr to record a crashing program: rr record <program> [args], then replay the recording with rr replay and navigate backward in time using reverse-next, reverse-step, and reverse-continue to identify the fault. When ready, run the included automation script to extract an execution trace: python3 scripts/crash_trace.py
High-intent search queries and answers about installing and using this skill.
Record-replay debugging captures a program's execution deterministically with rr record, then replay it with rr replay to step backward through crashes using reverse-next, reverse-step, and reverse-continue, letting you inspect state at any point leading to failure.
Yes, rr works with ASAN faults. Record the crashing program with rr record, replay with rr replay, and navigate backward to identify the memory safety violation and trace execution back to its root cause.
Record with rr record, replay with rr replay to navigate the crash, then run the included crash_trace.py script to automate trace extraction and state inspection across the recording, identifying the sequence leading to failure.
Yes, rr requires gdb on the host system. The record-replay engine captures deterministic execution, and gdb provides the reverse-execution commands (reverse-next, reverse-step, reverse-continue) to step backward through the trace.
Use record-replay when crashes are intermittent or timing-dependent; rr captures deterministic execution so you replay and inspect the exact same sequence repeatedly, making Heisenbugs reproducible and analyzable.
Reverse-step moves back one source line at a time within the current function; reverse-continue jumps back to the previous function call or breakpoint, letting you navigate backward at different granularities to isolate the fault.
deonmenezesRecord and replay native binaries with rr for deterministic reverse debugging.
open-foxAnalyze crash stacks and logs to produce root-cause reports with fix recommendations.
roberttmadsen13-delAutomate deterministic debugging of crashes and ASAN faults with rr record-replay.
curiositechInspect and replay node-level DAG execution traces to locate divergences.
