From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18304 invoked by alias); 15 Apr 2009 16:22:54 -0000 Received: (qmail 18293 invoked by uid 22791); 15 Apr 2009 16:22:52 -0000 X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 15 Apr 2009 16:22:47 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 178542BAB11; Wed, 15 Apr 2009 12:22:45 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 0bnnOUXKNIq4; Wed, 15 Apr 2009 12:22:45 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id D0B802BAB2B; Wed, 15 Apr 2009 12:22:44 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id 19F20F5BA6; Wed, 15 Apr 2009 09:22:42 -0700 (PDT) Date: Wed, 15 Apr 2009 16:22:00 -0000 From: Joel Brobecker To: Eli Zaretskii Cc: gdb-patches@sourceware.org Subject: Re: DWARF-related warnings in DJGPP build of GDB Message-ID: <20090415162242.GC7585@adacore.com> References: <834owqmdli.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <834owqmdli.fsf@gnu.org> User-Agent: Mutt/1.5.18 (2008-05-17) Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2009-04/txt/msg00319.txt.bz2 > During symbol reading, inner block not inside outer block in prompt_for_continue. > During symbol reading, inner block (0x61ab0-0x6b68b) not inside outer block (0x64c90-0x64d2f). > During symbol reading, Offset 174868 out of bounds for DW_AT_ranges attribute. > > Is this a GCC problem, a GDB problem, or something else? Should I be > worried? My GCC version is 3.4.3, in case that matters. What you can do is verify that the addresses are correctly read by GDB. You could try dumping the DWARF data if you have a tool that does that on your system. Otherwise, you could check the assembly file where prompt_for_continue is defined, and see if blocks indeed have the correct relationship in terms of block addresses. It could be the compiler emitting wrong debugging info, or the assembler/linker toolchain that screws up. Or, possibly, GDB is reading the information incorrectly, in which case, yes, you should be worried because that might cause a fair amount of grief depending on what's going wrong. I think this is unlikely, though. -- Joel