From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21780 invoked by alias); 27 Apr 2009 06:42:33 -0000 Received: (qmail 21766 invoked by uid 22791); 27 Apr 2009 06:42:33 -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; Mon, 27 Apr 2009 06:42:28 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 41BB02BAB8A; Mon, 27 Apr 2009 02:42:27 -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 ivsiufCaYqaD; Mon, 27 Apr 2009 02:42:27 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 0C7062BAB64; Mon, 27 Apr 2009 02:42:27 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id 2AE28F5924; Sun, 26 Apr 2009 23:42:25 -0700 (PDT) Date: Mon, 27 Apr 2009 06:55:00 -0000 From: Joel Brobecker To: sumanth Cc: Paul Pluzhnikov , gdb@sourceware.org Subject: Re: gcc - gdb compatibility issue Message-ID: <20090427064225.GN32765@adacore.com> References: <49F53FD6.5040209@redpinesignals.com> <8ac60eac0904262303q4f5b430ak5a14ba34f3dedd7f@mail.gmail.com> <20090427062828.GM32765@adacore.com> <49F55082.3020107@redpinesignals.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49F55082.3020107@redpinesignals.com> User-Agent: Mutt/1.5.18 (2008-05-17) 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: 2009-04/txt/msg00204.txt.bz2 > Joel ... Is there a way that i can avoid location lists generated by > my compiler and i am using DWARF 2 Not as far as I know. When we discovered that GDB 5.3 wasn't handling them very well (if at all, actually, I can't remember the symptoms anymore), we found that the fastest change until we could switch to a more recent debugger was to hack the compiler to avoid their generation. Olivier Hainque made the change, it was relatively localized. I suspect upgrading the debugger is going to be a lot easier than hacking the compiler. That being said, location lists are not necessarily the actual cause of your specific issue. It would be hard to tell without debugging the debugger itself. -- Joel