rr-debugger
starsforks
How to install rr-debugger?
gadievron/raptor/rr-debugger
$npx -y skills add gadievron/raptor --skill rr-debuggerDeterministic debugging with rr record-replay. Use when debugging crashes, ASAN faults, or when reverse execution is needed. Provides reverse-next, reverse-step, reverse-continue commands and crash trace extraction.
SKILL.md
| 1 | # rr Deterministic Debugger |
| 2 | |
| 3 | rr provides deterministic record-replay debugging with full reverse execution capabilities. |
| 4 | |
| 5 | ## Core Workflow |
| 6 | |
| 7 | 1. **Record**: `rr record <program> [args]` |
| 8 | 2. **Replay**: `rr replay` (enters gdb interface with reverse execution) |
| 9 | |
| 10 | ## Reverse Execution Commands |
| 11 | |
| 12 | All standard gdb commands work, plus reverse variants: |
| 13 | |
| 14 | - `reverse-next` / `rn`: Step back over function calls |
| 15 | - `reverse-step` / `rs`: Step back into functions |
| 16 | - `reverse-continue` / `rc`: Continue backward to previous breakpoint |
| 17 | - `reverse-stepi` / `rsi`: Step back one instruction |
| 18 | - `reverse-nexti` / `rni`: Step back over one instruction |
| 19 | |
| 20 | ## Crash Trace Extraction |
| 21 | |
| 22 | ### Regular Crashes |
| 23 | |
| 24 | After `rr record <crashing-program>`: |
| 25 | |
| 26 | ```bash |
| 27 | rr replay |
| 28 | # In gdb: |
| 29 | reverse-next 100 # Go back 100 steps (adjust N as needed) |
| 30 | # Now step forward to see execution leading to crash: |
| 31 | next |
| 32 | next |
| 33 | ... |
| 34 | ``` |
| 35 | |
| 36 | ### ASAN Crashes |
| 37 | |
| 38 | After `rr record <asan-program>`: |
| 39 | |
| 40 | ```bash |
| 41 | rr replay |
| 42 | # In gdb: |
| 43 | bt # View stack trace |
| 44 | up # Issue "up" commands until last app frame (before ASAN runtime) |
| 45 | break *$pc # Set breakpoint at that location |
| 46 | reverse-continue # Go back to last app instruction before ASAN |
| 47 | # Now step forward to see execution leading to fault: |
| 48 | next |
| 49 | next |
| 50 | ... |
| 51 | ``` |
| 52 | |
| 53 | ## Inspecting Variables and Memory |
| 54 | |
| 55 | Standard gdb commands work at any point: |
| 56 | |
| 57 | - `print <var>`: Print variable value |
| 58 | - `print *<ptr>`: Dereference pointer |
| 59 | - `x/<format> <address>`: Examine memory |
| 60 | - `x/10xb <addr>`: 10 bytes in hex |
| 61 | - `x/s <addr>`: String at address |
| 62 | - `info locals`: Show local variables |
| 63 | - `info args`: Show function arguments |
| 64 | |
| 65 | ## Source vs Assembly View |
| 66 | |
| 67 | - `list`: Show source code around current location |
| 68 | - `disassemble`: Show assembly around current location |
| 69 | - `layout src`: TUI source view |
| 70 | - `layout asm`: TUI assembly view |
| 71 | - `set disassemble-next-line on`: Show assembly with each step |
| 72 | |
| 73 | ## Automation Script |
| 74 | |
| 75 | Use `scripts/crash_trace.py` to automatically extract execution trace before crash. |
People who liked this also viewed
6 picksType
- azure-diagnosticsDebug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deploySkillsJul 2026
- systematic-debuggingUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesSkillsJul 2026
- safe-debugRigor Debug / Rigor Audit skill for deep learning research work. Use when the user pastes a traceback, terminal error, CUDA OOM, checkpoint load failure, shape mismatch, NaN loss symptom, or training SkillsMay 2026
- explore-runRigor Improve / Rigor Explore run leaf skill for bounded exploratory evidence in deep learning research repositories. Use when the researcher explicitly authorizes exploratory runs such as small-subseSkillsMay 2026
- minimal-run-and-auditRigor Run skill for README-first deep learning repo reproduction. Use when the task is specifically to capture or normalize evidence from the selected smoke test or documented inference or evaluation SkillsMay 2026
- insforge-debugUse when diagnosing problems in an InsForge project — reactive failures (SDK error object, HTTP 4xx/5xx, gateway timeout 502/503/504, edge function failure or timeout, login/OAuth/auth errors, RLS denSkillsJul 2026
