From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25869 invoked by alias); 14 Jul 2008 17:35:42 -0000 Received: (qmail 25862 invoked by uid 22791); 14 Jul 2008 17:35:42 -0000 X-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 14 Jul 2008 17:35:24 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id m6EHZJ2d027947; Mon, 14 Jul 2008 13:35:20 -0400 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [10.11.255.20]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m6EHZIgn021036; Mon, 14 Jul 2008 13:35:18 -0400 Received: from opsy.redhat.com (vpn-10-42.bos.redhat.com [10.16.10.42]) by pobox.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m6EHZI1P031044; Mon, 14 Jul 2008 13:35:18 -0400 Received: by opsy.redhat.com (Postfix, from userid 500) id 0E4D637814C; Mon, 14 Jul 2008 11:35:14 -0600 (MDT) To: Ian Lance Taylor Cc: Daniel Jacobowitz , Frysk List Subject: Re: Roadmap beginnings References: <20080711215243.GA30836@caradoc.them.org> From: Tom Tromey Reply-To: Tom Tromey X-Attribution: Tom Date: Mon, 14 Jul 2008 17:35:00 -0000 In-Reply-To: (Ian Lance Taylor's message of "Mon\, 14 Jul 2008 10\:18\:53 -0700") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Scanned-By: MIMEDefang 2.58 on 172.16.52.254 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/msg00038.txt.bz2 >>>>> "Ian" == Ian Lance Taylor writes: Tom> I'm looking around a bit to see if I can find specifics of what Tom> is wrong. Ian> I don't know if this counts as "expression parsing," but the most Ian> obvious problems that I encounter are the difficulties in working with Ian> STL objects. Given "std::vector v", I can't do "print v[0]". Ian> Given "std::vector::iterator p", I can't do "print *p". That is Ian> minimal required functionality for good C++ debugging. This needs to Ian> work smoothly for STL types and for user defined types. Thanks. I remember you mentioning this at the Summit, but I'd forgotten when sending the email. Ian> A related problem, which I don't know how to solve, is that many Ian> simple C++ accessors get inlined, and are not available when Ian> debugging. This makes it vastly more difficult to debug optimized C++ Ian> programs (indeed, this problem is more serious for me in practice than Ian> the debuginfo problems discussed at the summit). I have seen a few ideas kicked around: 1. Always emit the accessors out-of-line. 2. Emit DWARF code corresponding to the accessors. 3. Write Python code equivalent to the accessors and arrange for the debugger to invoke it in the appropriate situations. #1 seems like the obvious choice, aside from code size problems. Are those severe? Tom