This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFC] canonical linespec and multiple breakpoints ...
- From: Joel Brobecker <brobecker at adacore dot com>
- To: Jerome Guitton <guitton at adacore dot com>
- Cc: Tom Tromey <tromey at redhat dot com>, gdb-patches at sourceware dot org
- Date: Tue, 5 Jul 2011 08:17:04 -0700
- Subject: Re: [RFC] canonical linespec and multiple breakpoints ...
- References: <20110505162855.GA2546@adacore.com> <m3oc3gx48l.fsf@fleche.redhat.com> <83bozgmhil.fsf@gnu.org> <m3oc2pxjds.fsf@fleche.redhat.com> <83k4dcd1bh.fsf@gnu.org> <m3r56bdoh9.fsf@fleche.redhat.com> <m362nmarbv.fsf@fleche.redhat.com> <20110704192005.GQ2407@adacore.com> <20110705085308.GA16280@adacore.com>
> > My suggestion, in that case, is to make the list of selected
> > locations static. In other words, we do not add new locations
> > as they get discovered.
>
> I would suggest a slightly different rule: all breakpoints are still
> "multiple" by default. No "static" one. But, in the case of 'set
> multiple-symbols ask' and when one symbol is selected, then a
> breakpoint will be set, whose location will not be ambiguous (it will
> be "canonicalized"). So this "multiple" breakpoint will always
> resolve to only one location. If more than one choice is selected,
> same thing, with one breakpoint per choice.
>
> I'd rather avoid adding a special breakpoint kind for 'ask'. Just to
> keep it simple.
That would be fine with me. But, in a way, you're also deviating
from the general case by going from a one-bp-multiple-loc approach
to a multiple-bp-single-loc approach. Either way, I think it can
raise questions from the user...
--
Joel