From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13434 invoked by alias); 15 Apr 2009 19:26:39 -0000 Received: (qmail 13424 invoked by uid 22791); 15 Apr 2009 19:26:37 -0000 X-SWARE-Spam-Status: No, hits=0.2 required=5.0 tests=AWL,BAYES_00,RCVD_IN_JMF_BL,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Received: from mtaout3.012.net.il (HELO mtaout3.012.net.il) (84.95.2.7) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 15 Apr 2009 19:26:32 +0000 Received: from conversion-daemon.i_mtaout3.012.net.il by i_mtaout3.012.net.il (HyperSendmail v2004.12) id <0KI500I00PEE2R00@i_mtaout3.012.net.il> for gdb-patches@sourceware.org; Wed, 15 Apr 2009 22:26:29 +0300 (IDT) Received: from HOME-C4E4A596F7 ([84.229.34.97]) by i_mtaout3.012.net.il (HyperSendmail v2004.12) with ESMTPA id <0KI500BSPQ03XKH0@i_mtaout3.012.net.il>; Wed, 15 Apr 2009 22:26:28 +0300 (IDT) Date: Wed, 15 Apr 2009 19:26:00 -0000 From: Eli Zaretskii Subject: Re: DWARF-related warnings in DJGPP build of GDB In-reply-to: <20090415162242.GC7585@adacore.com> To: Joel Brobecker Cc: gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <83k55llnv6.fsf@gnu.org> References: <834owqmdli.fsf@gnu.org> <20090415162242.GC7585@adacore.com> X-IsSubscribed: yes 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/msg00344.txt.bz2 > Date: Wed, 15 Apr 2009 09:22:42 -0700 > From: Joel Brobecker > Cc: gdb-patches@sourceware.org > > > 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. What tools can do that? Is there a way of doing this with Binutils? > 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. Hints or an example for how to do that will be highly appreciated. > It could be the compiler emitting wrong debugging info, or the > assembler/linker toolchain that screws up. I will try to upgrade to newer Binutils and to GCC 3.4.4, and see if that helps. Thanks for the feedback.