rr-debugger / rr-debugger/rr

Add commands to explicitly start and stop diversions

Open
#1,622 12 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
10.7k
Forks
662
Avg merge
2d 3h
Merged PRs (30d)
2

Description

I'm trying to intentionally diverge from a replay by tweaking a variable but I get the following error:
Attempt to write memory outside diversion session

I did some searches online and just found roc' blog:
http://robert.ocallahan.org/2014/09/rr-20-released.html

It seems you can diverge for 'call' but not 'set'.

Ideally I'd like to do something like this:
diversion start
set shouldPrint = true
cont
<...>
diversion end

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing how the existing diversion behavior handles call, set, and cont, especially where the “Attempt to write memory outside diversion session” error is produced. Compare that behavior with the requested diversion start and diversion end command flow; done means variable changes can be scoped explicitly without that error and the command behavior is covered by tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
cli, devtools
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.