From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28424 invoked by alias); 7 Oct 2008 12:18:23 -0000 Received: (qmail 28414 invoked by uid 22791); 7 Oct 2008 12:18:23 -0000 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 07 Oct 2008 12:17:47 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 0AE342A9666; Tue, 7 Oct 2008 08:17:46 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id mnzolhTLra4O; Tue, 7 Oct 2008 08:17:45 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id CA5932A9643; Tue, 7 Oct 2008 08:17:45 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id 4C01DE7ACD; Tue, 7 Oct 2008 05:17:45 -0700 (PDT) Date: Tue, 07 Oct 2008 12:18:00 -0000 From: Joel Brobecker To: teawater Cc: "gdb-patches@sourceware.org" , Michael Snyder , Pedro Alves Subject: Re: [RFA] Displaced stepping just enable in non-stop mode Message-ID: <20081007121745.GH28138@adacore.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.2i 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: 2008-10/txt/msg00205.txt.bz2 > 2008-10-07 Hui Zhu > > * infrun.c (use_displaced_stepping): Displaced stepping just > enable in non-stop mode. There is still a piece missing. Namely, allow the user to force displaced-stepping in a mode that is not non-stop. Pedro suggested that we either change the maint command, or add a new one. How about changing the maint command into a mainstream command that's a tri-state: set use-displaced-stepping (auto|on|off) By default, it's "auto" which means that the debugger tries to determine from the situation whether it's necessary or not (basically if non-stop). But the user can then override the decision either way. -- Joel