From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17125 invoked by alias); 7 Apr 2007 20:20:56 -0000 Received: (qmail 17109 invoked by uid 22791); 7 Apr 2007 20:20:55 -0000 X-Spam-Check-By: sourceware.org Received: from ns1.anodized.com (HELO ns1.anodized.com) (204.15.208.61) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 07 Apr 2007 21:20:52 +0100 Received: from ns1.anodized.com (localhost [127.0.0.1]) by ns1.anodized.com (8.13.1/8.13.1) with ESMTP id l37KKkrx005642; Sat, 7 Apr 2007 13:20:46 -0700 Received: from 127.0.0.1 ([127.0.0.1] helo=ns1.anodized.com) by ASSP-nospam; 7 Apr 2007 13:20:46 -0700 Received: (from clayne@localhost) by ns1.anodized.com (8.13.1/8.13.1/Submit) id l37KKjOl005639; Sat, 7 Apr 2007 13:20:45 -0700 Date: Sat, 07 Apr 2007 20:20:00 -0000 From: Christopher Layne To: Eli Zaretskii , gdb-patches@sources.redhat.com Cc: Daniel Jacobowitz Subject: Re: [PATCH] Add support to control auto-display behavior Message-ID: <20070407202045.GD27568@ns1.anodized.com> References: <20070406110435.GC27568@ns1.anodized.com> <20070407172539.GB24650@caradoc.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070407172539.GB24650@caradoc.them.org> User-Agent: Mutt/1.5.11 X-Assp-Spam-Prob: 0.00000 X-Assp-Whitelisted: Yes X-Assp-Envelope-From: clayne@ns1.anodized.com X-Assp-Intended-For: drow@false.org gdb-patches@sources.redhat.com eliz@gnu.org 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: 2007-04/txt/msg00051.txt.bz2 On Sat, Apr 07, 2007 at 01:25:39PM -0400, Daniel Jacobowitz wrote: > On Fri, Apr 06, 2007 at 04:52:59PM +0300, Eli Zaretskii wrote: > > > initially setup some auto-displays and then begin stepping. I don't see > > > any reason why, in the event an object is not accessible, the auto-display > > > should be disabled. > > > > Thanks. I agree that it's a good idea to have an option to control > > this, unless we agree that what you want as an option should be how > > GDB behaves in all cases. > > I think changing the behavior unconditionally would be a good idea. > Showing the error is more sensible; it's always bugged me that my > displays get turned off (and sometimes deleted instead of disabled - I > do not know why that happens). My thinking is the same as well - it bugged me enough that I decided to do something about it. Kinda funny, I went on a research hunt for exactly where the line of output "avoid infinite recursion" had been added, hoping to find some rationale, and it looks like it's been there since the early 90s. I originally had it as "disable-on-error" but changed it to "strict" and non-default as I wasn't sure if the original intended behavior had a real reason for being there. If it's okay with you guys, I'll restructure the patch to fix some of the documentation issues and semantics to assume it as default behavior. -cl