From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 73323 invoked by alias); 11 Sep 2015 07:01:29 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 73309 invoked by uid 89); 11 Sep 2015 07:01:29 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.3 required=5.0 tests=AWL,BAYES_50,RCVD_IN_DNSWL_NONE,SPF_SOFTFAIL autolearn=no version=3.3.2 X-HELO: mtaout22.012.net.il Received: from mtaout22.012.net.il (HELO mtaout22.012.net.il) (80.179.55.172) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 11 Sep 2015 07:01:28 +0000 Received: from conversion-daemon.a-mtaout22.012.net.il by a-mtaout22.012.net.il (HyperSendmail v2007.08) id <0NUI00D003724L00@a-mtaout22.012.net.il> for gdb-patches@sourceware.org; Fri, 11 Sep 2015 10:01:00 +0300 (IDT) Received: from HOME-C4E4A596F7 ([84.94.185.246]) by a-mtaout22.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NUI00CZN3HOYE50@a-mtaout22.012.net.il>; Fri, 11 Sep 2015 10:01:00 +0300 (IDT) Date: Fri, 11 Sep 2015 07:01:00 -0000 From: Eli Zaretskii Subject: Re: [PATCH v2 17/17] infrun: scheduler-locking reverse In-reply-to: <1441954298-25298-18-git-send-email-markus.t.metzger@intel.com> To: Markus Metzger Cc: palves@redhat.com, gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <83io7h4eze.fsf@gnu.org> References: <1441954298-25298-1-git-send-email-markus.t.metzger@intel.com> <1441954298-25298-18-git-send-email-markus.t.metzger@intel.com> X-IsSubscribed: yes X-SW-Source: 2015-09/txt/msg00206.txt.bz2 > From: Markus Metzger > Cc: gdb-patches@sourceware.org, 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.