From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20733 invoked by alias); 24 Mar 2015 18:07:41 -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 20717 invoked by uid 89); 24 Mar 2015 18:07:41 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham 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; Tue, 24 Mar 2015 18:07:35 +0000 Received: from int-mx13.intmail.prod.int.phx2.redhat.com (int-mx13.intmail.prod.int.phx2.redhat.com [10.5.11.26]) by mx1.redhat.com (Postfix) with ESMTPS id CCEB7BACD8 for ; Tue, 24 Mar 2015 18:07:34 +0000 (UTC) Received: from [127.0.0.1] (ovpn01.gateway.prod.ext.ams2.redhat.com [10.39.146.11]) by int-mx13.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id t2OI7XqU008344 for ; Tue, 24 Mar 2015 14:07:34 -0400 Message-ID: <5511A7E5.2000205@redhat.com> Date: Tue, 24 Mar 2015 18:07: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: gdb-patches@sourceware.org Subject: Re: [PATCH 0/4] Make "set scheduler-locking step" depend on user intention, only References: <1426084798-1032-1-git-send-email-palves@redhat.com> In-Reply-To: <1426084798-1032-1-git-send-email-palves@redhat.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-SW-Source: 2015-03/txt/msg00805.txt.bz2 On 03/11/2015 02:39 PM, Pedro Alves wrote: > Currently, "set scheduler-locking step" is a bit odd. The manual > documents it as being optimized for stepping, so that focus of > debugging does not change unexpectedly, but then it says that > sometimes other threads may run, and thus focus may indeed change > unexpectedly... A user can then be excused to get confused and wonder > why does GDB behave like this. > > I don't think a user should have to know about details of how "next" > or whatever other run control command is implemented internally to > understand when does the "scheduler-locking step" setting take effect. > > Thus this series makes "set scheduler-locking step" hold threads > depending on whether the _command_ the user entered was a stepping > command [step/stepi/next/nexti], or not. More details in patch #3. > > The rest of the series is related groundwork and cleaning up. > > Tested on x86_64 Fedora 20, native and gdbserver. I pushed this in now. Thanks, Pedro Alves