From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7829 invoked by alias); 9 Sep 2015 13:54:32 -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 7705 invoked by uid 89); 9 Sep 2015 13:54:31 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.4 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,SPF_HELO_PASS,T_RP_MATCHES_RCVD autolearn=no version=3.3.2 X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Wed, 09 Sep 2015 13:54:29 +0000 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (Postfix) with ESMTPS id F2B6D461EA; Wed, 9 Sep 2015 13:54:27 +0000 (UTC) Received: from [127.0.0.1] (ovpn01.gateway.prod.ext.ams2.redhat.com [10.39.146.11]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id t89DsQGo007931; Wed, 9 Sep 2015 09:54:27 -0400 Message-ID: <55F03A12.80307@redhat.com> Date: Wed, 09 Sep 2015 13:54:00 -0000 From: Pedro Alves User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: Markus Metzger CC: gdb-patches@sourceware.org Subject: Re: [PATCH 17/17] infrun: scheduler-locking reverse References: <1441794909-32718-1-git-send-email-markus.t.metzger@intel.com> <1441794909-32718-18-git-send-email-markus.t.metzger@intel.com> In-Reply-To: <1441794909-32718-18-git-send-email-markus.t.metzger@intel.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-SW-Source: 2015-09/txt/msg00130.txt.bz2 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. Thanks, Pedro Alves