From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8045 invoked by alias); 22 Nov 2006 13:35:23 -0000 Received: (qmail 7898 invoked by uid 22791); 22 Nov 2006 13:35:22 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Wed, 22 Nov 2006 13:35:12 +0000 Received: from drow by nevyn.them.org with local (Exim 4.63) (envelope-from ) id 1GmsFn-0008GH-BK; Wed, 22 Nov 2006 08:35:07 -0500 Date: Wed, 22 Nov 2006 13:35:00 -0000 From: Daniel Jacobowitz To: Benjamin Kosnik Cc: Paul Pogonyshev , libstdc++@gcc.gnu.org, gdb@sourceware.org Subject: Re: setting breakpoints with C++ typedef names [was: Re: debug information] Message-ID: <20061122133506.GA31609@nevyn.them.org> Mail-Followup-To: Benjamin Kosnik , Paul Pogonyshev , libstdc++@gcc.gnu.org, gdb@sourceware.org References: <200611191342.48724.pogonyshev@gmx.net> <20061121100701.6b980f48.bkoz@redhat.com> <200611212225.28377.pogonyshev@gmx.net> <20061122130341.a4436ce2.bkoz@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20061122130341.a4436ce2.bkoz@redhat.com> User-Agent: Mutt/1.5.13 (2006-08-11) X-IsSubscribed: yes 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: 2006-11/txt/msg00151.txt.bz2 On Wed, Nov 22, 2006 at 01:03:41PM +0100, Benjamin Kosnik wrote: > I suggest reporting this to the gdb list (gdb@sourceware.org). You > might want to title that email something like "setting breakpoints with > C++ typedef names" or something more descriptive. Here, I've done that > for you. > > To me, it looks like enough information is present in the debuginfo to > support this kind of usage. However, I am no expert in this area. I don't think that GDB will ever support this. It's one of a batch of C++ improvements that would be nice to have, but getting it right would require most of a C++ front end. And for various reasons, I don't think that reusing the g++ front end would be practical. We could probably get it to work in strictly limited cases, though. -- Daniel Jacobowitz CodeSourcery