From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12877 invoked by alias); 24 Nov 2006 21:28:19 -0000 Received: (qmail 12867 invoked by uid 22791); 24 Nov 2006 21:28:18 -0000 X-Spam-Check-By: sourceware.org Received: from mail.gmx.net (HELO mail.gmx.net) (213.165.64.20) by sourceware.org (qpsmtpd/0.31) with SMTP; Fri, 24 Nov 2006 21:28:13 +0000 Received: (qmail invoked by alias); 24 Nov 2006 21:28:10 -0000 Received: from unknown (EHLO [80.94.234.93]) [80.94.234.93] by mail.gmx.net (mp044) with SMTP; 24 Nov 2006 22:28:10 +0100 X-Authenticated: #16844820 From: Paul Pogonyshev To: Martin Sebor Subject: Re: setting breakpoints with C++ typedef names [was: Re: debug information] Date: Fri, 24 Nov 2006 21:28:00 -0000 User-Agent: KMail/1.7.2 Cc: Benjamin Kosnik , libstdc++@gcc.gnu.org, gdb@sourceware.org References: <200611191342.48724.pogonyshev@gmx.net> <20061122130341.a4436ce2.bkoz@redhat.com> <456762E8.2050703@roguewave.com> In-Reply-To: <456762E8.2050703@roguewave.com> MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200611242331.59900.pogonyshev@gmx.net> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 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/msg00170.txt.bz2 Martin Sebor wrote: > Benjamin Kosnik wrote: > >>But still function names include full type name: `b 'bar(basic_pod)''. > >>Not much of a problem in this case, but sometimes the full name is very > >>long... > > > > > > Oh. I finally understand you. Yes, this is a drag. > > > > You want to be able to do: > > > > (gdb) b bar(ipod) > > > > instead of > > > > (gdb) b bar(basic_pod) > > This is especially troublesome when the real type is private to > the implementation, as in, for example, > > void foo (std::map::iterator); > > In order for a user to set a breakpoint on foo they need to know > that the type of libstdc++'s map::iterator is really called > std::_Rb_tree_iterator > > (and something completely different when using a different > implementation of the library). Another important problem (and most important to me, since I set up breakpoints using Tab-completion anyway) is that it makes backtraces and similar stuff virtually unreadable. Paul