From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29864 invoked by alias); 28 Dec 2003 11:24:22 -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 29857 invoked from network); 28 Dec 2003 11:24:21 -0000 Received: from unknown (HELO monty-python.gnu.org) (199.232.76.173) by sources.redhat.com with SMTP; 28 Dec 2003 11:24:21 -0000 Received: from [207.232.27.5] (helo=WST0054) by monty-python.gnu.org with asmtp (Exim 4.24) id 1AaZzG-0001Dm-Jt for gdb@sources.redhat.com; Sun, 28 Dec 2003 07:25:39 -0500 Date: Sun, 28 Dec 2003 11:24:00 -0000 Message-Id: From: Eli Zaretskii To: gdb@sources.redhat.com Subject: inner block not inside outer block Reply-to: Eli Zaretskii X-SW-Source: 2003-12/txt/msg00271.txt.bz2 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.) TIA