From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2026 invoked by alias); 15 Jul 2004 13:55:15 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 2013 invoked from network); 15 Jul 2004 13:55:14 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sourceware.org with SMTP; 15 Jul 2004 13:55:14 -0000 Received: from drow by nevyn.them.org with local (Exim 4.34 #1 (Debian)) id 1Bl6gu-0000wA-3W; Thu, 15 Jul 2004 09:54:28 -0400 Date: Thu, 15 Jul 2004 14:09:00 -0000 From: Daniel Jacobowitz To: Michael Elizabeth Chastain Cc: gdb@sources.redhat.com, rolandz@poczta.fm Subject: Re: How to setup a breakpoint on constructor Message-ID: <20040715135427.GA3545@nevyn.them.org> Mail-Followup-To: Michael Elizabeth Chastain , gdb@sources.redhat.com, rolandz@poczta.fm References: <20040715113103.E988A4B104@berman.michael-chastain.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040715113103.E988A4B104@berman.michael-chastain.com> User-Agent: Mutt/1.5.5.1+cvs20040105i X-SW-Source: 2004-07/txt/msg00165.txt.bz2 On Thu, Jul 15, 2004 at 07:31:03AM -0400, Michael Chastain wrote: > Hi Roland, > > Would you like to try a makeshift and experimental patch? > > ftp://ftp.shout.net/pub/users/mec/ctor-dtor-base.patch > > (Patch attached to this message too). > > You have to apply this to the libiberty/ subdirectory of a > recent gdb, such as gdb 6.1.1, and then rebuild gdb. > > There's a lot of doco in the patch but it rambles. > The basic idea is that I patched the demangler so that > it demangles the different ctor's with different names: > > A::A() > A::A$base() > A::A$allocate() > > I don't know if it's a good idea for gdb to work this way, > but I think it's worth getting some user feedback. > > Testing: I haven't run the test suite with this. > I did test a small program (testsuite/gdb.cp/derivation.cc) > and it works the way I think it should. FYI, I implemented this once. The users who tried it didn't like it at all. -- Daniel Jacobowitz