seer/tests/hellorr

Record a RR session.

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

    $ export _RR_TRACE_DIR=/nas/erniep/Development/seer/tests/hellorr/rr
    $ rr record -n hellorr

    Or...

    $ rr record -n --output-trace-dir=/path/to/rr/trace-directory  hellorr arg1 arg2
    $ rr record -n --output-trace-dir=`pwd`/rr hellorr one two three


Replay the RR session in Seer.

    $ seergdb --rr /path/to/rr/trace-directory



THE FOLLOWING IS OLD!!

This method allowed Seer to connect to a RR debug server via a host:port.
I've deprecated this in favor of running 'rr replay' directly.

    Replay the RR session in gdb.

        $ export _RR_TRACE_DIR=/nas/erniep/Development/seer/tests/hellorr/rr

        $ rr replay

    Using RR in a gui debugger. Basically, attach to the rr server port.

        https://github.com/rr-debugger/rr/wiki/Using-rr-in-an-IDE

        $ export _RR_TRACE_DIR=/nas/erniep/Development/seer/tests/hellorr/rr

        $ rr replay -s 50505 -k

        $ rr replay -s 50505 -k
        Launch gdb with
        gdb '-l' '10000' '-ex' 'set sysroot /' '-ex' 'target extended-remote 127.0.0.1:50505' /nas/erniep/Development/seer/tests/hellorr/hellorr

    In a different terminal, use "RR" method in the Debug dialog and connect to "127.0.0.1:50505".
    You may need to tell Seer to load the executable for the symbols.

        $ export _RR_TRACE_DIR=/nas/erniep/Development/seer/tests/hellorr/rr

        $ seergdb --rr localhost:50505 --sym hellorr