Crash when replaying a trace of Mixxx (part 3)
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.7k
- Forks
- 662
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 2
Description
Replaying a trace of Mixxx recorded with rr built from master (at cfafbfd788d1a9cc765129242d67077fb0967ef3) causes a crash. To work around #3672 I stopped the pipewire daemon before recording the execution.
I noticed that I can avoid the crash by passing the flag -n to rr record
So, here are some logs for @khuey:
rr recordandrr replay -aoutput: mixxx_replay_crash_part_3.txtgdbbacktrace: mixxx_replay_crash_part_3_gdb_backtrace.txtrr dump -p -m -b: mixxx_replay_crash_part_3_dump.txt.gz
rr record -nandrr dump -p -m -boutput: mixxx_replay_crash_part_3_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 with the attached rr record/rr replay -a output, GDB backtrace, and rr dump files, then compare them with the rr record -n dump. Reproduce the Mixxx trace if available and isolate why normal recording crashes while -n avoids it. Done means the replay crash has a confirmed cause and a fix or clearly documented next step.
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
- 30/100