From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28869 invoked by alias); 27 Apr 2009 06:55:35 -0000 Received: (qmail 28858 invoked by uid 22791); 27 Apr 2009 06:55:34 -0000 X-SWARE-Spam-Status: No, hits=-1.6 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from mail.redpinesignals.com (HELO mail.redpinesignals.com) (203.196.161.92) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 27 Apr 2009 06:55:26 +0000 Received: from [192.168.40.84] ([192.168.40.84]) (authenticated user sumanth.gundapneni@redpinesignals.com) by mail.redpinesignals.com; Mon, 27 Apr 2009 12:21:29 +0530 Message-ID: <49F554B7.400@redpinesignals.com> Date: Mon, 27 Apr 2009 13:19:00 -0000 From: sumanth User-Agent: Thunderbird 2.0.0.16 (X11/20080707) MIME-Version: 1.0 To: Joel Brobecker CC: Paul Pluzhnikov , gdb@sourceware.org Subject: Re: gcc - gdb compatibility issue References: <49F53FD6.5040209@redpinesignals.com> <8ac60eac0904262303q4f5b430ak5a14ba34f3dedd7f@mail.gmail.com> <20090427062828.GM32765@adacore.com> <49F55082.3020107@redpinesignals.com> <20090427064225.GN32765@adacore.com> In-Reply-To: <20090427064225.GN32765@adacore.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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/msg00205.txt.bz2 Joel , if you don't mind can you brief me on this " 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. " Thanks in advance , Sumanth G Joel Brobecker wrote: >> 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. > >