Crash when replaying a trace of Mixxx (part 2)
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.7k
- Forks
- 662
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 2
Description
I just tried to debug Mixxx with rr built from master (at 285e117e7baa1f13a9631916af74b7281ad7742b) after I saw that @rocallahan closed #3667.
Unfortunately, it still crashes.
Here are the logs @khuey asked me last time:
rr recordandrr replay -aoutput: mixxx_replay_crash_part_2.txtrr record -nandrr replay -aoutput: mixxx_replay_crash_part_2_no_syscall_buffer.txtrr record -nandrr dump -p -m -boutput: mixxx_replay_crash_part_2_no_syscall_buffer_dump.txt.gz
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 the Mixxx trace with the reported rr master revision and the rr record, rr replay -a, and rr dump -p -m -b commands. Compare the attached logs, including the no-syscall-buffer runs, and consider the issue complete when replay no longer crashes for this trace.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, linux
- Domain
- devtools, operating-systems, reverse-engineering
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100