-
Notifications
You must be signed in to change notification settings - Fork 581
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash when replaying a trace of Mixxx (part 3) #3673
Comments
Which exact CPU are you using? |
Here's my
I executed |
This is a PMU issue; we've requested a PMU interrupt at a certain ticks value and we're not getting it:
If you replay multiple times does it fail the same way at the same point every time? Do you have access to an Intel box you can try recording and replaying on? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Replaying a trace of Mixxx recorded with rr built from master (at cfafbfd) 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
torr record
So, here are some logs for @khuey:
rr record
andrr replay -a
output: mixxx_replay_crash_part_3.txtgdb
backtrace: mixxx_replay_crash_part_3_gdb_backtrace.txtrr dump -p -m -b
: mixxx_replay_crash_part_3_dump.txt.gzrr record -n
andrr dump -p -m -b
output: mixxx_replay_crash_part_3_no_syscall_buffer_dump.txt.gzThe text was updated successfully, but these errors were encountered: