From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2712 invoked by alias); 13 Jun 2006 23:13:11 -0000 Received: (qmail 2702 invoked by uid 22791); 13 Jun 2006 23:13:10 -0000 X-Spam-Check-By: sourceware.org Received: from potter.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 13 Jun 2006 23:13:09 +0000 Received: (qmail 23213 invoked from network); 13 Jun 2006 23:13:07 -0000 Received: from unknown (HELO localhost) (jimb@127.0.0.2) by mail.codesourcery.com with ESMTPA; 13 Jun 2006 23:13:07 -0000 To: Steven Johnson Cc: gdb-patches@sourceware.org Subject: Re: psymtab not in symtab warning patch References: <448BB966.3050200@sakuraindustries.com> From: Jim Blandy Date: Tue, 13 Jun 2006 23:13:00 -0000 In-Reply-To: <448BB966.3050200@sakuraindustries.com> (Steven Johnson's message of "Sun, 11 Jun 2006 17:34:14 +1100") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2006-06/txt/msg00205.txt.bz2 Steven Johnson writes: > Please consider the attached patch. > > It allows the "PC 0x??? in psymtab but not in symtab" warning to be > "toggled off". The reason for this, is for whatever reason I get it > heaps with my PPC Assembler code. There doesn't appear to be any > obvious incantation to control it or prevent it when building the asm > files, so i've given up trying. The attached patch retains the current > behaviour, but if someone is being inundated by the warning, which > happens when it occurs, they can turn it off, and at least continue > debugging OK. > > Obviously finding out why it happens is far better, but i know nothing > about dwarf debug information, or the psymtab or symtab stuff, so i'm > not going to be productive in finding a better answer. I'm happy to debug this, if you can get me an executable to work with. Large is fine, just something you can share. As far as the patch goes --- we probably want to use a complaint here; see 'complaints.h', and see how they're used in dwarf2read.c. That will automatically limit the number of times you see the complaint, the default being zero.