From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8092 invoked by alias); 12 Jun 2005 17:47:31 -0000 Mailing-List: contact insight-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: insight-owner@sourceware.org Received: (qmail 8083 invoked by uid 22791); 12 Jun 2005 17:47:29 -0000 Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Sun, 12 Jun 2005 17:47:29 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11/8.12.11) with ESMTP id j5CHlRn0030970 for ; Sun, 12 Jun 2005 13:47:27 -0400 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [172.16.52.156]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id j5CHlRu12177; Sun, 12 Jun 2005 13:47:27 -0400 Received: from localhost.localdomain (sebastian-int.corp.redhat.com [172.16.52.221]) by pobox.corp.redhat.com (8.12.8/8.12.8) with ESMTP id j5CHlQgd019276; Sun, 12 Jun 2005 13:47:27 -0400 Subject: Re: Numerous Warnings for RTTI Symbol Not Found From: Keith Seitz To: Vale Group Cc: "insight@sources.redhat.com" In-Reply-To: <000c01c56ee0$cdeb3280$277c183f@brockman> References: <42896CAD.60504@sakuraindustries.com> <4289CFD6.6040306@sakuraindustries.com> <1116286740.4493.9.camel@lindt.uglyboxes.com> <428A79EE.4080307@sakuraindustries.com> <42A58351.7090608@sakuraindustries.com> <1118087604.4531.80.camel@lindt.uglyboxes.com> <42A607F4.6030307@sakuraindustries.com> <1118105313.4531.136.camel@lindt.uglyboxes.com> <000c01c56ee0$cdeb3280$277c183f@brockman> Content-Type: text/plain Date: Sun, 12 Jun 2005 17:47:00 -0000 Message-Id: <1118598446.4517.2.camel@lindt.uglyboxes.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-SW-Source: 2005-q2/txt/msg00115.txt.bz2 On Sat, 2005-06-11 at 16:52 -0700, Vale Group wrote: > What causes those warnings to appear? GDB still hasn't fixed these kinds of problems. I think most gdb developers are so used to these little annoyances that they just ignore them, which is easy to do when it just results in a line being printed to the terminal. > Is it possible to suppress the warnings? (Each one must be individually > acknowledged to continue!) Yes, edit gdb/gdbtk/library/interface.tcl. The procedure "gdbtk_tcl_warning" contains a list of error messages which will simply go to the console window without opening a dialog. When you've done that, please submit a patch. For this small change, you probably don't need to worry about an assignment if you don't have one. Keith