Building And Installing

rocallahan edited this page Jan 27, 2017 · 39 revisions



sudo dnf install \
  ccache cmake make gcc gcc-c++ gdb libgcc libgcc.i686 \
  glibc-devel glibc-devel.i686 libstdc++-devel libstdc++-devel.i686 zlib-devel \
  python-pexpect man-pages ninja-build


sudo apt-get install ccache cmake make g++-multilib gdb \
  pkg-config libz-dev realpath python-pexpect manpages-dev git zlib1g-dev \


mkdir rr
cd rr
git clone
mkdir obj
cd obj

Then to use make and the system default compiler to build:

cmake ../rr
make -j8
make test
make install

Or to use clang and Ninja to build (faster!):

CC=clang CXX=clang++ cmake -G Ninja ../rr
ninja-build test
ninja-build install

Use ninja rather than ninja-build on Ubuntu.

Hardware/software requirements

Supported microarchitectures are Intel architectures newer than Merom and Penryn, i.e. Nehalem and beyond.

/proc/sys/kernel/perf_event_paranoid must be <= 1 for rr to work efficiently. Some distros set it to 2 or higher, in which case you either need to set it to 1 or use rr record -n, which is slow.

If you run rr in a virtual machine, MAKE SURE VIRTUALIZATION OF PERF COUNTERS IS ENABLED. The virtual machines that do work with rr and the settings required are listed below. If a virtual machine isn't on this list, then it cannot be used with rr.

  • VMWare Workstation 9 / Fusion 7 & 8: The default is for counter virtualization to be disabled. You have to enable it in the VM settings (advanced processor options). Also add monitor_control.disable_hvsim_clusters = true to the VM's .vmx file (more information).
  • Qemu: On QEMU command line use
    -cpu host
  • Libvirt/KVM: Specify CPU passthrough in domain XML definition:
    <cpu mode='host-passthrough'/>
  • Xen: insert instructions here...
  • Digital Ocean: The only VPS provider known to work with RR.

VirtualBox does not work at this time because it doesn't support PMU virtualization. Because it's open-source, someone just needs to contribute that...

If rr isn't working at all, run dmesg|grep PMU. If you get output like

[    0.311273] Performance Events: Fam15h core perfctr, Broken PMU hardware detected, using software events only.
[    0.311279] Failed to access perfctr msr (MSR c0010201 is 25c6c8c489)

then something is disabled in your BIOS, or perhaps you have a broken hardware configuration, or you're in a VM without PMU virtualization.

Build prerequisites

First, install the compiler toolchain and additional packages. python-pexpect is required to run unit tests. man-pages is optional but strongly recommended if you'll be doing rr development. See the package lists at the top of this page.


rr uses the CMake build system, which is able to generate multiple build environments. This enables you to choose whichever build driver you prefer to use. The commands below show building rr in a separate obj directory. This is recommended because cmake generates a lot of auxiliary files.

To use Eclipse

cd ../
mkdir obj
cd obj
cmake -G "Eclipse CDT4 - Unix Makefiles" ../rr

Next, import the project into Eclipse. By default Eclipse will automatically build the project when files change. You can force Eclipse to rebuild the project by pressing Ctrl-B.

To use Makefiles

cd ../
mkdir obj
cd obj
cmake ../rr

Then the command


will build the project.

Building and installing with a custom prefix

cmake -DCMAKE_INSTALL_PREFIX=<prefix> ../rr
make install

PaX kernels

If your kernel is a PaX kernel (if these words don't mean anything to you, you can skip this paragraph), then you will need to disable MPROTECT on the built files bin/rr, bin/rr_exec_stub and bin/rr_exec_stub_32.

If you use PT header flags, for example, you should run

paxctl -cm bin/rr bin/rr_exec_stub bin/rr_exec_stub_32

in your build directory.


See this page.


Be sure to read the usage instructions before running tests.

rr has a suite of tests in $rr/src/test. To run the tests with minimal output,

make test

or with full output

make check

The video_capture test may briefly turn on an attached camera, if you have one --- do not be alarmed!

Each test consists of a C source file and a .run file, which is a shell script. To run an individual BASIC_TEST $test outside the harness:

cd $rr/src/test
bash -b $rr '' $test

To run a non-basic test:

cd $rr/src/test
bash $ -b $rr '' $test

To run a non-basic test in 32-bit mode:

cd $rr/src/test
bash $ -b $rr '' $test_32