This is the mail archive of the
mailing list for the GDB project.
Re: [PATCH 17/17] infrun: scheduler-locking reverse
- From: Pedro Alves <palves at redhat dot com>
- To: Markus Metzger <markus dot t dot metzger at intel dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Wed, 09 Sep 2015 14:54:26 +0100
- Subject: Re: [PATCH 17/17] infrun: scheduler-locking reverse
- Authentication-results: sourceware.org; auth=none
- References: <1441794909-32718-1-git-send-email-markus dot t dot metzger at intel dot com> <1441794909-32718-18-git-send-email-markus dot t dot metzger at intel dot com>
On 09/09/2015 11:35 AM, Markus Metzger wrote:
> 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.
> By making the current behaviour a scheduler-locking option, we allow the user
> to change it. Since it is the current behaviour, this new option is also
> the new default.
Hmm. The code looks fine. But I should point out that if a user
has "schedlock step" in their gdbinit, they'll miss this. Fedora's gdb
actually currently defaults to schedlock=step.