This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [patch] Fix internal error on breaking at a multi-locations caller
- From: Joel Brobecker <brobecker at adacore dot com>
- To: Tom Tromey <tromey at redhat dot com>
- Cc: Jan Kratochvil <jan dot kratochvil at redhat dot com>, gdb-patches at sourceware dot org
- Date: Tue, 28 Apr 2009 13:32:35 -0700
- Subject: Re: [patch] Fix internal error on breaking at a multi-locations caller
- References: <20090309220736.GA27259@host0.dyn.jankratochvil.net> <m3ljpqq30d.fsf@fleche.redhat.com>
> Based on the documentation of `break', and also my mental model of
> debugging with gdb, I think that the best behavior here would be to
> simply set a single breakpoint here -- the one corresponding to the
> instance that is currently being executed. Then we don't have to
> worry about the other instances, and we won't set odd breakpoints
> elsewhere.
>
> What do you (or anybody) think of that?
That's a good point. I actually had a different interpretation
of the "break" command without arguments, but the documentation
is very specific about it. I agree with you.
--
Joel