From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25068 invoked by alias); 14 Jul 2008 17:34:21 -0000 Received: (qmail 25054 invoked by uid 22791); 14 Jul 2008 17:34:21 -0000 X-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 14 Jul 2008 17:33:57 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id 0ACE798200; Mon, 14 Jul 2008 17:33:56 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id D81279813B; Mon, 14 Jul 2008 17:33:55 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1KIRvv-0002Ry-70; Mon, 14 Jul 2008 13:33:55 -0400 Date: Mon, 14 Jul 2008 17:34:00 -0000 From: Daniel Jacobowitz To: Ian Lance Taylor Cc: Tom Tromey , Frysk List Subject: Re: Roadmap beginnings Message-ID: <20080714173355.GA9326@caradoc.them.org> References: <20080711215243.GA30836@caradoc.them.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2008-05-11) X-IsSubscribed: yes Mailing-List: contact frysk-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: frysk-owner@sourceware.org X-SW-Source: 2008-q3/txt/msg00037.txt.bz2 On Mon, Jul 14, 2008 at 10:18:53AM -0700, Ian Lance Taylor wrote: > I don't know if this counts as "expression parsing," but the most > obvious problems that I encounter are the difficulties in working with > STL objects. Given "std::vector v", I can't do "print v[0]". > Given "std::vector::iterator p", I can't do "print *p". That is > minimal required functionality for good C++ debugging. This needs to > work smoothly for STL types and for user defined types. Right. This is not the expression parsing quagmire - it's definitely bugs that need to be fixed, but the solutions are (should be) pretty simple. Tom and I talked about approaches to use Python support, shipped with the STL implementation, to provide debugger implementations of inlined operators that are never emitted out of line. > It would also be nice if gdb could do template parameter defaulting, > although that is rather less important as tab completion can take care > of it. Better debug info is definitely required for this. DWARF defines the necessary bits, but neither GCC nor GDB implement them. > A related problem, which I don't know how to solve, is that many > simple C++ accessors get inlined, and are not available when > debugging. This makes it vastly more difficult to debug optimized C++ > programs (indeed, this problem is more serious for me in practice than > the debuginfo problems discussed at the summit). Actually, see above. I assumed that was your problem with the STL operators. If there are other problems, please let us know - maybe after Tom finishes the Bugzilla migration he's got almost done :-) Thanks for the examples. -- Daniel Jacobowitz CodeSourcery