From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28592 invoked by alias); 12 Mar 2007 21:23:40 -0000 Received: (qmail 28582 invoked by uid 22791); 12 Mar 2007 21:23:39 -0000 X-Spam-Check-By: sourceware.org Received: from nile.gnat.com (HELO nile.gnat.com) (205.232.38.5) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 12 Mar 2007 21:23:33 +0000 Received: from localhost (localhost [127.0.0.1]) by filtered-nile.gnat.com (Postfix) with ESMTP id 9B04948CC1C; Mon, 12 Mar 2007 17:23:31 -0400 (EDT) Received: from nile.gnat.com ([127.0.0.1]) by localhost (nile.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 09685-01-9; Mon, 12 Mar 2007 16:23:31 -0500 (EST) Received: from takamaka.act-europe.fr (unknown [70.71.0.212]) by nile.gnat.com (Postfix) with ESMTP id 16DBE48CBAE; Mon, 12 Mar 2007 17:23:31 -0400 (EDT) Received: by takamaka.act-europe.fr (Postfix, from userid 1000) id 6725FE7B38; Mon, 12 Mar 2007 14:24:05 -0700 (PDT) Date: Mon, 12 Mar 2007 21:23:00 -0000 From: Joel Brobecker To: Maxim Grigoriev Cc: gdb@sourceware.org, Bob Wilson , Marc Gauthier Subject: Re: GDB (mis)behavior depends on DWARF DW_TAG_compile_unit data Message-ID: <20070312212405.GM14401@adacore.com> References: <45F5B929.3050406@hq.tensilica.com> <20070312204857.GA20515@caradoc.them.org> <45F5C0D3.90002@hq.tensilica.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <45F5C0D3.90002@hq.tensilica.com> User-Agent: Mutt/1.4.2.2i Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2007-03/txt/msg00173.txt.bz2 > If you think it's a generic GDB problem I can fix it. I have to fix it > anyway on Xtensa GDB. I don't see how it can be Xtensa-specific. > Xtensa GCC compiler DWARF is consistent with native GCC 4.1.1 compiler > on my Linux box. So if this is a compiler problem ( which I doubt ) > it seems to be pretty generic. With the information you have given us, all I can say is that GDB should be able to handle the situation, so we do have a bug somewhere. Whether it is in GCC or GDB is still an open question as far as I can tell. Have you checked the line-table as well in both cases? There is a very convenient command that gives you the list of lines known by GDB for any given file: -symbol-list-lines. It's a MI command, but you should be able to use it from the GDB prompt using "interpreter-exe mi -symbol-list-lines" followed by the filename. -- Joel