From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16939 invoked by alias); 30 Aug 2011 15:09:10 -0000 Received: (qmail 16930 invoked by uid 22791); 30 Aug 2011 15:09:09 -0000 X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,RP_MATCHES_RCVD,SPF_HELO_PASS X-Spam-Check-By: sourceware.org Received: from smtp-out.google.com (HELO smtp-out.google.com) (216.239.44.51) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 30 Aug 2011 15:08:55 +0000 Received: from wpaz33.hot.corp.google.com (wpaz33.hot.corp.google.com [172.24.198.97]) by smtp-out.google.com with ESMTP id p7UF8sIL023641 for ; Tue, 30 Aug 2011 08:08:54 -0700 Received: from gyg4 (gyg4.prod.google.com [10.243.50.132]) by wpaz33.hot.corp.google.com with ESMTP id p7UF8q1m028947 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for ; Tue, 30 Aug 2011 08:08:53 -0700 Received: by gyg4 with SMTP id 4so6833503gyg.34 for ; Tue, 30 Aug 2011 08:08:52 -0700 (PDT) Received: by 10.90.138.10 with SMTP id l10mr5310058agd.126.1314716932729; Tue, 30 Aug 2011 08:08:52 -0700 (PDT) MIME-Version: 1.0 Received: by 10.90.138.10 with SMTP id l10mr5310050agd.126.1314716932426; Tue, 30 Aug 2011 08:08:52 -0700 (PDT) Received: by 10.90.84.9 with HTTP; Tue, 30 Aug 2011 08:08:52 -0700 (PDT) In-Reply-To: <20110830142115.GA2650@host1.jankratochvil.net> References: <20110830014851.78030246131@ruffy.mtv.corp.google.com> <20110830091623.GA5329@host1.jankratochvil.net> <1314698487.57217.YahooMailRC@web86705.mail.ird.yahoo.com> <20110830115627.GA21003@host1.jankratochvil.net> <1314708109.43672.YahooMailRC@web86707.mail.ird.yahoo.com> <20110830142115.GA2650@host1.jankratochvil.net> Date: Tue, 30 Aug 2011 15:09:00 -0000 Message-ID: Subject: Re: [RFC] stept, nextt, finisht, untilt, continuet From: Doug Evans To: Jan Kratochvil Cc: pfee@talk21.com, gdb-patches@sourceware.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-System-Of-Record: true 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/msg00607.txt.bz2 On Tue, Aug 30, 2011 at 7:21 AM, Jan Kratochvil wrote: > My original post was that I believe the new `*t' commands were invented m= ore > because `set scheduler-locking step' is not default+working. =A0I guess s= uch > idea would not arise at all otherwise. =A0Any new configuration options a= nd/or > more commands are bad when the same functionality can be reached otherwis= e. My patch is partially because "set scheduler-locking step" doesn't apply to next, but it also doesn't apply to other commands. *And* at least as importantly, if not more so, I don't always want "set scheduler-locking step", and having to remember to switch global state back and forth is extremely clumsy! Blech. In my sessions the setting of scheduler-locking is far more dynamic, a global state setting is the wrong solution. I kinda like adding a new option to step,next,etc., but writing wrappers in python doesn't add new commands to gdb proper. One of the reasons we have python.