From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11313 invoked by alias); 16 Aug 2002 01:14:51 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 11211 invoked from network); 16 Aug 2002 01:14:51 -0000 Received: from unknown (HELO crack.them.org) (65.125.64.184) by sources.redhat.com with SMTP; 16 Aug 2002 01:14:51 -0000 Received: from nevyn.them.org ([66.93.61.169] ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 17fVhV-0003oW-00; Thu, 15 Aug 2002 20:14:53 -0500 Received: from drow by nevyn.them.org with local (Exim 3.35 #1 (Debian)) id 17fVhu-0006J7-00; Thu, 15 Aug 2002 21:15:18 -0400 Date: Thu, 15 Aug 2002 18:14:00 -0000 From: Daniel Jacobowitz To: Kevin Buettner Cc: Andrew Cagney , gdb@sources.redhat.com Subject: Re: Issue an internal warning on first deprecated function call Message-ID: <20020816011518.GA24067@nevyn.them.org> Mail-Followup-To: Kevin Buettner , Andrew Cagney , gdb@sources.redhat.com References: <3D5C248D.4030003@ges.redhat.com> <1020815223303.ZM7495@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1020815223303.ZM7495@localhost.localdomain> User-Agent: Mutt/1.5.1i X-SW-Source: 2002-08/txt/msg00173.txt.bz2 On Thu, Aug 15, 2002 at 03:33:03PM -0700, Kevin Buettner wrote: > On Aug 15, 6:00pm, Andrew Cagney wrote: > > > The problem behind this was discussed in: > > http://sources.redhat.com/ml/gdb/2001-03/msg00227.html > > > > The idea is to issue an internal-warning on the first call to a > > deprecated [multi-arch] function. > > > > The intent is to better alert the user to the possability that their GDB > > is on its last legs. > > > > Thoughts? Variations on the idea? > > I think we should strive to just fix (eliminate) the calls to > deprecated functions instead. However, there are times when it's too > hard or can't be sufficiently tested. > > A variation on the above idea is to scan a newly created gdbarch > struct to see if any deprecated functions are being used. If so, > print only one message per session. (I.e, instead of seeing N > messages from N deprecated function, you'd only see one message for > the whole lot.) The nuisance factor could be cut back even further if > we arrange for .gdbinit setting which can be used to disable such > messages. > > This variation will also cause the message to be printed at a more > predictable time, probably either at startup or just after a ``file'' > operation. I definitely like this idea. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer