From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28996 invoked by alias); 18 Jul 2004 05:05:12 -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 28984 invoked from network); 18 Jul 2004 05:05:11 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sourceware.org with SMTP; 18 Jul 2004 05:05:11 -0000 Received: from drow by nevyn.them.org with local (Exim 4.34 #1 (Debian)) id 1Bm3qW-0003aB-Vp; Sun, 18 Jul 2004 01:04:21 -0400 Date: Sun, 18 Jul 2004 18:44:00 -0000 From: Daniel Jacobowitz To: Eli Zaretskii Cc: Michael Elizabeth Chastain , gdb@sources.redhat.com, rolandz@poczta.fm Subject: Re: How to setup a breakpoint on constructor Message-ID: <20040718050420.GA13745@nevyn.them.org> Mail-Followup-To: Eli Zaretskii , Michael Elizabeth Chastain , gdb@sources.redhat.com, rolandz@poczta.fm References: <20040717205225.56BC04B104@berman.michael-chastain.com> <9003-Sun18Jul2004071107+0300-eliz@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9003-Sun18Jul2004071107+0300-eliz@gnu.org> User-Agent: Mutt/1.5.5.1+cvs20040105i X-SW-Source: 2004-07/txt/msg00231.txt.bz2 On Sun, Jul 18, 2004 at 07:11:07AM +0200, Eli Zaretskii wrote: > > Date: Sat, 17 Jul 2004 16:52:25 -0400 (EDT) > > From: mec.gnu@mindspring.com (Michael Elizabeth Chastain) > > > > > Coincidentally that's what the entire discussion of 1:N breakpoints > > > last year was about but no one has had time to implement it. > > > > Right. > > > > 1:N breakpoints are better than A::A$base(), but it's been 3 years since > > the ctor-breakpoint issue came up, and we don't have anything at all > > yet. > > So how about setting a breakpoint on all of the places, like Daniel > suggested? > > > But if someone breaks in A::A$base() and then says 'break 1000' to get > > into the middle of the function (which I do a lot), then they would get > > the breakpoint in the wrong copy! So even if we disambiguate the > > names, the 1:N nature of multiple ctors shines through. > > Can't we put a breakpoint on all instances in that case as well? Yes. But this requires a certain amount of user interface design and implementation hackery that no one has done; every time I tried I got bogged down in some dependency. -- Daniel Jacobowitz