This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: : Re: [RFC] multiple breakpoints from FILE:LINE
- From: Daniel Jacobowitz <drow at false dot org>
- To: Paul Koning <pkoning at equallogic dot com>
- Cc: comar at adacore dot com, hilfingr at gnat dot com, gdb at sourceware dot org
- Date: Sun, 15 Jan 2006 11:45:00 -0500
- Subject: Re: : Re: [RFC] multiple breakpoints from FILE:LINE
- References: <43C9AAA8.2030605@adacore.com> <17354.31047.417000.385481@gargle.gargle.HOWL>
On Sun, Jan 15, 2006 at 11:33:11AM -0500, Paul Koning wrote:
> Cyrille> I believe it would be worthwhile to have 2 different break
> Cyrille> commands: - break - break-multiple (or whatever other more
> Cyrille> appropriate name)
>
> Cyrille> break-multiple would have the semantics advocated by Daniel
> Cyrille> (break automatically on all relevant locations)
>
> Cyrille> break, instead of presenting a menu, would issue an error of
> Cyrille> the kind:
>
> Cyrille> (gdb) break FILENAME:LINENUM multiple choices for this
> Cyrille> breakpoint, please use any of the following: break-multiple
> Cyrille> FILENAME:LINENUM break FILENAME:instance1.function:LINENUM
Well, I think this should be just one command, and maybe have "break"
in the CLI issue a warning (just like it does now). But that's a
relatively small change.
The instance1.function syntax handles one important Ada case, but
there's plenty of other cases; for instance, there can be an arbitrary
chain of inlining. I'm not convinced that there's any practical way to
get it right.
> Nice. What syntax would you use for the two constructors, and three
> destructors, that have the same C++ names?
I've yet to see a compelling reason to break on one constructor and not
the other. Most users don't even know the difference between when each
is called.
--
Daniel Jacobowitz
CodeSourcery