`rr replay` fails with "Event::Event(EncodedEvent): Assertion `0 == e.data'"
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.7k
- Forks
- 662
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 2
Description
rharwood@fedproxy:~/gssproxy/proxy$ rr replay
rr: /home/rharwood/rr/src/Event.cc:52: Event::Event(EncodedEvent): Assertion `0 == e.data' failed.
rharwood@fedproxy:~/gssproxy/proxy$ echo $_RR_TRACE_DIR
/tmp/rr/
rharwood@fedproxy:~/gssproxy/proxy$ ls -R /tmp/rr
/tmp/rr:
gssproxy-0 latest-trace
/tmp/rr/gssproxy-0:
args_env data data_header events mmaps tasks version
rharwood@fedproxy:~/gssproxy/proxy$ lsb_release -a
LSB Version: :core-4.1-amd64:core-4.1-noarch
Distributor ID: Fedora
Description: Fedora release 22 (Twenty Two)
Release: 22
Codename: TwentyTwo
rharwood@fedproxy:~/gssproxy/proxy$
The problem occurs whether I build from source or use the provided RPMs. Please let me know if there is any more information I can provide.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing rr replay with the /tmp/rr/gssproxy-0 trace and inspect Event.cc:52, where the assertion is reported. Compare the trace files (events, data, data_header, and version) with the source and RPM builds. Done means identifying why this trace cannot be replayed and confirming a corrected replay or a documented diagnosis.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, linux
- Domain
- devtools, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100