From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-9923-listarch-gdb=sourceware.cygnus.com@sources.redhat.com>
Received: (qmail 12587 invoked by alias); 16 Aug 2002 13:31:57 -0000
Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb/>
List-Post: <mailto:gdb@sources.redhat.com>
List-Help: <mailto:gdb-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-owner@sources.redhat.com
Received: (qmail 12580 invoked from network); 16 Aug 2002 13:31:56 -0000
Received: from unknown (HELO systemhalted) (24.112.140.233)
  by sources.redhat.com with SMTP; 16 Aug 2002 13:31:56 -0000
Received: from carlos by systemhalted with local (Exim 3.35 #1 (Debian))
	id 17fhB6-00039x-00
	for <gdb@sources.redhat.com>; Fri, 16 Aug 2002 09:30:12 -0400
Date: Fri, 16 Aug 2002 06:31:00 -0000
From: Carlos O'Donell <carlos@baldric.uwo.ca>
To: gdb@sources.redhat.com
Subject: Re: Issue an internal warning on first deprecated function call
Message-ID: <20020816133012.GC11845@systemhalted>
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.4i
X-Useless-Header: oooohhmmm, chant the email mantra...
X-SW-Source: 2002-08/txt/msg00181.txt.bz2

> 
> 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.

I like the 'once per session' idea.
Can we make the that message a rather largish banner?

c.