From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4589 invoked by alias); 15 Aug 2002 22:01:05 -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 2807 invoked from network); 15 Aug 2002 22:00:47 -0000 Received: from unknown (HELO localhost.redhat.com) (216.138.202.10) by sources.redhat.com with SMTP; 15 Aug 2002 22:00:47 -0000 Received: from ges.redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id DFB5B3C82 for ; Thu, 15 Aug 2002 18:00:45 -0400 (EDT) Message-ID: <3D5C248D.4030003@ges.redhat.com> Date: Thu, 15 Aug 2002 15:01: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: gdb@sources.redhat.com Subject: Issue an internal warning on first deprecated function call Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-08/txt/msg00168.txt.bz2 Hello, 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? Andrew