rr-debugger / rr-debugger/rr

Assertion fails while reverse-continuing after setting watchpoint

Open
#1,894 4 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

Hey,

While trying to reverse continue after setting a watchpoint I get the following error:

rr: /home/sean/Documents/git/rr/rr/src/ReplayTimeline.cc:213: void rr::ReplayTimeline::mark_after_singlestep(const rr::ReplayTimeline::Mark&, const rr::ReplayResult&): Assertion `i + 1 < mark_vector.size() && mark_vector[i + 1] == m.ptr' failed.

On a similar issue I saw you requested the output with RR_LOG=GdbConnection set, so I've gathered that and you can find it at https://gist.github.com/SeanHeelan/a424c20e0d63c255755a6205174daaee

I am using the latest version from the master branch (1a1663373f8a4ca0d2c27e7a8c14cc35d642c93d), on Fedora 24 with a 4.8.4 kernel. The target application is a variant of the klee symbolic execution engine.

If you need any further details let me know!

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

Inspect src/ReplayTimeline.cc at mark_after_singlestep and reproduce reverse-continue after setting a watchpoint, using the RR_LOG=GdbConnection output and environment details in the issue. Done means identifying why the assertion fails and preventing the crash while preserving reverse-continuation behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
devtools, reverse-engineering
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.