From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3030 invoked by alias); 30 Aug 2011 14:21:45 -0000 Received: (qmail 3020 invoked by uid 22791); 30 Aug 2011 14:21:44 -0000 X-SWARE-Spam-Status: No, hits=-6.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,RP_MATCHES_RCVD,SPF_HELO_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 30 Aug 2011 14:21:23 +0000 Received: from int-mx01.intmail.prod.int.phx2.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id p7UELMxt021713 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 30 Aug 2011 10:21:22 -0400 Received: from host1.jankratochvil.net (ovpn-116-38.ams2.redhat.com [10.36.116.38]) by int-mx01.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id p7UELJY1026964 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 30 Aug 2011 10:21:21 -0400 Received: from host1.jankratochvil.net (localhost [127.0.0.1]) by host1.jankratochvil.net (8.14.4/8.14.4) with ESMTP id p7UELId9002861; Tue, 30 Aug 2011 16:21:18 +0200 Received: (from jkratoch@localhost) by host1.jankratochvil.net (8.14.4/8.14.4/Submit) id p7UELGBb002853; Tue, 30 Aug 2011 16:21:16 +0200 Date: Tue, 30 Aug 2011 14:21:00 -0000 From: Jan Kratochvil To: pfee@talk21.com Cc: Doug Evans , gdb-patches@sourceware.org Subject: Re: [RFC] stept, nextt, finisht, untilt, continuet Message-ID: <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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1314708109.43672.YahooMailRC@web86707.mail.ird.yahoo.com> User-Agent: Mutt/1.5.21 (2010-09-15) 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/msg00600.txt.bz2 On Tue, 30 Aug 2011 14:41:49 +0200, pfee@talk21.com wrote: > Another point, regarding "continue". In non-stop mode, there's a "-a" flag to > continue all threads. Would it be worth using the same flag when in > scheduler-locking mode to cause the entire process to resume? One can use `set scheduler-locking off' in such case. The point of `set scheduler-locking step' is that it should affect the most common uses of GDB. Stepping/Nexting single thread but continue-ing all the threads. One can alwaye use `set scheduler-locking' as an override if s/he has some specific needs. My original post was that I believe the new `*t' commands were invented more because `set scheduler-locking step' is not default+working. I guess such idea would not arise at all otherwise. Any new configuration options and/or more commands are bad when the same functionality can be reached otherwise. Thanks, Jan