From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4909 invoked by alias); 30 Aug 2011 10:01:44 -0000 Received: (qmail 4901 invoked by uid 22791); 30 Aug 2011 10:01:44 -0000 X-SWARE-Spam-Status: No, hits=-1.4 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE X-Spam-Check-By: sourceware.org Received: from nm2-vm0.bt.bullet.mail.ukl.yahoo.com (HELO nm2-vm0.bt.bullet.mail.ukl.yahoo.com) (217.146.182.242) by sourceware.org (qpsmtpd/0.43rc1) with SMTP; Tue, 30 Aug 2011 10:01:29 +0000 Received: from [217.146.183.195] by nm2.bt.bullet.mail.ukl.yahoo.com with NNFMP; 30 Aug 2011 10:01:27 -0000 Received: from [217.146.183.203] by tm1.bt.bullet.mail.ukl.yahoo.com with NNFMP; 30 Aug 2011 10:01:27 -0000 Received: from [127.0.0.1] by omp1001.bt.mail.ukl.yahoo.com with NNFMP; 30 Aug 2011 10:01:27 -0000 Received: (qmail 57274 invoked by uid 60001); 30 Aug 2011 10:01:27 -0000 Received: from [94.72.254.2] by web86705.mail.ird.yahoo.com via HTTP; Tue, 30 Aug 2011 11:01:27 BST References: <20110830014851.78030246131@ruffy.mtv.corp.google.com> <20110830091623.GA5329@host1.jankratochvil.net> Message-ID: <1314698487.57217.YahooMailRC@web86705.mail.ird.yahoo.com> Date: Tue, 30 Aug 2011 10:01:00 -0000 From: pfee@talk21.com Subject: Re: [RFC] stept, nextt, finisht, untilt, continuet To: Jan Kratochvil , Doug Evans Cc: gdb-patches@sourceware.org In-Reply-To: <20110830091623.GA5329@host1.jankratochvil.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes 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 X-SW-Source: 2011-08/txt/msg00590.txt.bz2 > On Tue, 30 Aug 2011 03:48:51 +0200, Doug Evans wrote: > > Sometimes I want to run with scheduler-locking on, but having to turn = it=20 on, > > perform the command, and remember to turn it off afterwards is annoyin= g. >=20 > Please no, Fedora already has default `set scheduler-locking step' becau= se > this is what the users expect from the stepping commands. >=20 > What are the reasons for not using `set scheduler-locking step'? >=20 I like the 'step' mode of scheduler-locking, but often wish it applied to t= he=20 "next" command, not just step. My suggestion would be to create a "set scheduler-locking next" mode in whi= ch=20 both "step" and "next" operate with other threads locked out. Thanks, Paul