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: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- To: Tom Tromey <tromey at redhat dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Wed, 27 Jul 2011 18:14:50 +0200
- 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> <m3hb68q0no.fsf@fleche.redhat.com>
On Tue, 26 Jul 2011 21:53:15 +0200, Tom Tromey wrote:
> So, a slightly different approach to solving this would be to make
> breakpoints capture their location set at the "point of resolution" --
> either immediately, or for a pending breakpoint, the first time it hits.
> Then, provide some additional syntax to make a "permanently pending"
> breakpoint.
I find it OK. With various lazy reads it may be more useful your unapplied
read-debuginfos-by-background-thread patch. If it finds later an existing
breakpoint could have another location in the newly read debuginfo it could
warn the user s/he should use the "permanently pending" form next time.
But that feature may be too far from now.
Thanks,
Jan