From: Markus Metzger Date: Fri, 25 Oct 2024 13:53:04 +0000 (+0000) Subject: btrace, infrun: replay scheduler locking only depends on to-be-resumed thread X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=9c29dc7d143ae518132eeea098e1774cc4be9b04;p=thirdparty%2Fbinutils-gdb.git btrace, infrun: replay scheduler locking only depends on to-be-resumed thread Similar to the parent commit, simplify schedlock_applies() by only checking the argument thread. When resuming that thread, GDB will automatically stop replaying its inferior. The replay state of other inferiors is not considered by user_visible_resume_ptid(), so let's not consider them in schedlock_applies(), either. --- diff --git a/gdb/infrun.c b/gdb/infrun.c index dccd72dc308..9b26ba88621 100644 --- a/gdb/infrun.c +++ b/gdb/infrun.c @@ -3195,8 +3195,7 @@ schedlock_applies (struct thread_info *tp) || (scheduler_mode == schedlock_step && tp->control.stepping_command) || (scheduler_mode == schedlock_replay - && target_record_will_replay (minus_one_ptid, - execution_direction))); + && target_record_will_replay (tp->ptid, execution_direction))); } /* When FORCE_P is false, set process_stratum_target::COMMIT_RESUMED_STATE