Add support for reproducing target program executions using `rr`

[yskzalloc]

Initially, I attempted to create reproducers using strace like log, but further research showed that this approach is almost impossible in practice. Therefore, a new strategy should be considered to improve reproducibility.

Proposal

• Implement a reproducible mode that stores program executions using rr(--rr).
• Allow storing and replaying the target program with rr to provide deterministic reproduction of issues.

Motivation

• strace is insufficient for building reliable reproducers due to the complexity and nondeterminism of system interactions.
• rr provides a deterministic record-and-replay model, making it well-suited for kernel/user-space issue reproduction.
• Improves debugging and sharing of reproducible test cases across different environments.

Use cases

• Debugging hard-to-reproduce crashes and race conditions.
• Creating a standardized way to replay execution under reproducible conditions.

[yskzalloc]

Basic usage for rr

• https://github.com/rr-debugger/rr/wiki/Usage

$ rr record ./my_app
$ rr replay -a # --autopilot, no gdb session
$ rr pack ~/.local/share/rr/my_app-1
$ rr replay -a ~/.local/share/rr/my_app-1

Using rr pack
rr traces can be made portable with the rr pack command. This will pack the trace directory to eliminate duplicate files and to include all files needed for transportation. As such, it allows you to gather traces on one machine and move them to another machine for debugging. It also makes it easy to run recordings for different versions of the software, since the trace no longer relies on hard links to the executable files.

• https://github.com/rr-debugger/rr/wiki/Trace-Portability