Re: Breakpoints in constructors

[Daniel Jacobowitz <drow@false.org>]

On Tue, Jan 03, 2006 at 06:35:45PM +0530, Amit Kale wrote:
> Hi All,
> 
> I've rebased the breakpoints in constructors patch to current cvs. It's 
> attached for reviews and a submission into mainline gdb after any 
> modifications/improvements as per gdb gurus' suggestions.
> 
> I ran gdb testsuite with this patch and found several failures which were 
> absent in a cvs-built gdb. They are mainly related to "advance" command. I am 
> looking at the failures and trying to fix them. I'll send an update if I can 
> fix any of them.
> 
> I'll very much appreciate any feedback for this.

Hi Amit, and sorry for not getting back to you about this last time you
posted it on gdb@.

The short version is that I believe this is roughly the right approach,
but not quite.  I posted a work-in-progress patch some time ago that
takes a slightly different approach:

Date: Sun, 13 Mar 2005 19:38:24 -0500
From: Daniel Jacobowitz <drow@false.org>
Subject: RFC: First stab at breakpoints in multiple locations

You might want to take a look at that thread, if you haven't already,
to see what I mean.  The basic difference is that instead of "break
Foo::Foo" setting multiple breakpoints, it would set only one
breakpoint, but that breakpoint would be associated with multiple PC
values.

I can't really tell from your patch what cases you do handle or don't;
do breakpoints on constructors by name work?  How about by line number?

-- 
Daniel Jacobowitz
CodeSourcery