Re: MI: changing breakpoint location

Eli Zaretskii
2006-03-17T11:40:07Z

> Date: Thu, 16 Mar 2006 18:12:15 -0500
> From: Daniel Jacobowitz <drow@false.org>
> Cc: Vladimir Prus <ghost@cs.msu.su>, gdb@sources.redhat.com
>
> On Fri, Mar 17, 2006 at 12:07:27PM +1300, Nick Roberts wrote:
> > > Now, I have to delete the old breakpoint and create the new one, which is
> > > workable, but not convenient.
> >
> > I don't find a problem with that, but it would be nice if when a program is
> > edited and recompiled that GDB could track the line number. So, for example
> > if the breakpoint is on line 10, say, and lines 4 and 5 are deleted, then
> > after recompiling and restarting, its on line 8. I think Visual Stuio has
> > this feature. I have no idea how easy/hard it would be to implement.
>
> Hard. RMS once asked for a simpler version of this, which is to track
> breakpoints by line number relative to the start of the function; but
> really we ought to be able to do this very well.

If we have a volunteer, the fact that it's hard is not very relevant ;-)

> I'm thinking something like "remember a couple lines of context, if you
> can find the same context, adjust the breakpoint and warn the user".
> But there's some risk of it landing in the wrong place; I don't know
> how to do it reliably but I bet a motivated developer would come up
> with something :-)

At least the front end could help here, since this happens when
sources are edited.