From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4985 invoked by alias); 18 Sep 2008 22:27:37 -0000 Received: (qmail 4977 invoked by uid 22791); 18 Sep 2008 22:27:36 -0000 X-Spam-Check-By: sourceware.org Received: from vms173005pub.verizon.net (HELO vms173005pub.verizon.net) (206.46.173.5) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 18 Sep 2008 22:26:58 +0000 Received: from [10.10.1.168] ([209.190.166.162]) by vms173005.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPA id <0K7E00B6YWZSM6H9@vms173005.mailsrvcs.net> for insight@sourceware.org; Thu, 18 Sep 2008 17:26:17 -0500 (CDT) Date: Fri, 19 Sep 2008 14:27:00 -0000 From: John Fine Subject: Re: Can't debug x86_64 C++ programs. In-reply-to: <48D2C56C.2020105@redhat.com> To: Keith Seitz Cc: insight@sourceware.org Message-id: <48D2D57F.6070004@verizon.net> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7bit References: <48D024D1.3000107@verizon.net> <48D0A482.8060000@redhat.com> <48D0FC0A.2000207@verizon.net> <48D2C56C.2020105@redhat.com> User-Agent: Thunderbird 2.0.0.16 (Windows/20080708) X-IsSubscribed: yes Mailing-List: contact insight-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: insight-owner@sourceware.org X-SW-Source: 2008-q3/txt/msg00072.txt.bz2 Keith Seitz wrote: > The good news is that it is now my job to make gdb a better c++ > debugger, so my knowledge grows every day. Can I put in an early request (maybe you've heard this one already) to do something about the absurdly long function names. In viewing disassembly, you get function name + offset as one of the items on the line, but in typical templated code the function name is so long that the actual disassembly is pushed off the right edge of the display. I can't think of a decent method to make a more concise display of function name (maybe you can). But failing that, I think you need an option to drop it entirely. Or is there such an option already that I just haven't found? I'm not very good at using gdb. function name + offset was never such valuable information that we really needed it and when it is too bulky to use, it should go away. For Insight's SRC+ASM view, I think putting the source line number on each line in both panels would help a lot (again if that option is already there, I'm not expert). While that is less critical for gdb itself than for a GUI, I think it would be a very useful option in gdb itself (disassemble with the source line number shown on each line of disassembly). Hopefully other GUI's layered on gdb would give the user access to that feature. If you're not totally turning off optimization, any user looking at a disassembly spends a lot of time figuring out which source line is connected to each asm line. It would make more sense for the debugger to just display the compiler's version of that information.