From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25311 invoked by alias); 28 Dec 2003 18:46:57 -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 25304 invoked from network); 28 Dec 2003 18:46:57 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sources.redhat.com with SMTP; 28 Dec 2003 18:46:57 -0000 Received: from drow by nevyn.them.org with local (Exim 4.30 #1 (Debian)) id 1AafwG-0007bS-AW; Sun, 28 Dec 2003 13:46:56 -0500 Date: Sun, 28 Dec 2003 18:46:00 -0000 From: Daniel Jacobowitz To: Eli Zaretskii Cc: gdb@sources.redhat.com Subject: Re: inner block not inside outer block Message-ID: <20031228184655.GA29177@nevyn.them.org> Mail-Followup-To: Eli Zaretskii , gdb@sources.redhat.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.1i X-SW-Source: 2003-12/txt/msg00272.txt.bz2 On Sun, Dec 28, 2003 at 01:25:53PM +0200, Eli Zaretskii wrote: > I've just compiled GDB 6.0 with DJGPP (patches to fix what was broken > to follow shortly) using GCC 3.3.2, and while trying the classic > "break main; run" test in GDB debugging itself, I see several messages > like this: > > During symbol reading, inner block not inside outer block in internal_vproblem > During symbol reading, inner block (0x1-0xffe289b8) not inside outer block (0x11b09a-0x11b2e0) > During symbol reading, block at 0x1 out of order > > I've read the description of these messages in the manual, which seems > to say that, as a user, I shouldn't worry about them. What I'm not > sure about is what should I do as a _GDB_maintainer_. Is this a GDB > bug? a GCC bug? something specific to the DJGPP port of either or both > of them? something else? Should I report that somewhere or is it a > known problem? > > (In case it matters, this GDB was compiled with DWARF-2 debug info.) This means that the address range of either the psymtab or symtab is incorrect. It could be either incorrect debug information (probably in the linker relocation handling) or it could be a GDB bug (probably in dwarf2read.c). You can't use readelf but I assume you can get one of the other DWARF debugging tools to work - maybe dwarfdump - and figure out what the actual bounds of the blocks in question are? -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer