This is the mail archive of the mailing list for the GDB project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH v2 17/17] infrun: scheduler-locking reverse

> From: Markus Metzger <>
> Cc:, Eli Zaretskii <>
> Date: Fri, 11 Sep 2015 08:51:38 +0200
> Record targets behave as if scheduler-locking were on during replay/reverse
> execution.  Add a new scheduler-locking option "reverse" to make this implicit
> behaviour explicit.  It behaves like "on" during reverse/replay execution and
> like "off" during normal execution.

I suggest to call this value "replay" instead.  "Reverse" has other
meanings that can interfere with its mnemonic value.

> 2015-09-11  Markus Metzger <>
> gdb/
> 	* NEWS: Announce new scheduler-locking mode.
> 	* infrun.c (schedlock_reverse): New.
> 	(scheduler_enums): Add schedlock_reverse.
> 	(scheduler_mode): Change default to schedlock_reverse.
> 	(user_visible_resume_ptid): Handle schedlock_reverse.
> 	(clear_proceed_status_thread): Stop replaying if resumed thread is
> 	not replaying.
> 	(schedlock_applies): Handle schedlock_reverse.
> 	(_initialize_infrun): Document new scheduler-locking mode.
> 	* record-btrace.c (record_btrace_resume): Remove code to stop other
> 	threads when not replaying the resumed thread.
> doc/
> 	* gdb.texinfo (All-Stop Mode): Describe new scheduler-locking mode.

OK for the documentation parts.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]