Google Git
Sign in
android / toolchain / rr / refs/tags/upstream/5.4.0
commitc2878731db4ed3d16ee999fa74fe2a5fb7edb0e6[log] [tgz]
authorRobert O'Callahan <robert@ocallahan.org>Thu Oct 29 12:13:49 2020 +1300
committerRobert O'Callahan <robert@ocallahan.org>Thu Oct 29 12:13:49 2020 +1300
treefe0b5bee658e701c9c74b0d1ff8d1fea4c02c071
parentc4cc0232c490328a490c90ce00e99d565fa4ac0d [diff]
Bump version to 5.4.0.
1 file changed
tree: fe0b5bee658e701c9c74b0d1ff8d1fea4c02c071
  1. include/
  2. scripts/
  3. snap/
  4. src/
  5. third-party/
  6. .clang-format
  7. .gitignore
  8. CMakeLists.txt
  9. CODE_OF_CONDUCT.md
  10. configure
  11. CONTRIBUTING.md
  12. LICENSE
  13. README.md
  14. rr.spec
  15. Vagrantfile
README.md

Overview

rr is a lightweight tool for recording, replaying and debugging execution of applications (trees of processes and threads). Debugging extends gdb with very efficient reverse-execution, which in combination with standard gdb/x86 features like hardware data watchpoints, makes debugging much more fun. More information about the project, including instructions on how to install, run, and build rr, is at https://rr-project.org. The best technical overview is currently the paper Engineering Record And Replay For Deployability: Extended Technical Report.

Or go directly to the installation and building instructions.

Please contribute! Make sure to review the pull request checklist before submitting a pull request.

If you find rr useful, please add a testimonial.

System requirements

  • Linux kernel ≥ 3.11 is required (for PTRACE_SETSIGMASK).
  • rr currently requires either:
  • Running in a VM guest is supported, as long as the VM supports virtualization of hardware performance counters. (VMware and KVM are known to work; Xen does not.)