From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31200 invoked by alias); 16 Aug 2002 01:36:24 -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 30976 invoked from network); 16 Aug 2002 01:36:22 -0000 Received: from unknown (HELO localhost.redhat.com) (216.138.202.10) by sources.redhat.com with SMTP; 16 Aug 2002 01:36:22 -0000 Received: from ges.redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id E9F303C03; Thu, 15 Aug 2002 21:36:20 -0400 (EDT) Message-ID: <3D5C5714.90407@ges.redhat.com> Date: Thu, 15 Aug 2002 18:36:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.0) Gecko/20020810 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Daniel Jacobowitz , Kevin Buettner Cc: gdb@sources.redhat.com Subject: Re: Issue an internal warning on first deprecated function call References: <3D5C248D.4030003@ges.redhat.com> <1020815223303.ZM7495@localhost.localdomain> <20020816011518.GA24067@nevyn.them.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-08/txt/msg00174.txt.bz2 FYI, The intent was for only one internal-warning message to appear per debug session. Given that an internal-warning message is pretty ``on-the-nose'' I don't think I could get away with any more than one. I wrote: > > The problem behind this was discussed in: > > http://sources.redhat.com/ml/gdb/2001-03/msg00227.html (recommended read) > > The idea is to issue an internal-warning on the first call to a > > deprecated [multi-arch] function. For architecture methods, it's pretty easy -- hook the ``set_gdbarch_deprecated...()'' calls. For things like write_register_bytes() it is less so. enjoy, Andrew