Re: MI: changing breakpoint location

Eli Zaretskii
2006-03-18T11:19:40Z

> Date: Fri, 17 Mar 2006 12:22:54 -0500
> From: Daniel Jacobowitz <drow@false.org>
> Cc: David Daney <ddaney@avtrex.com>, Nick Roberts <nickrob@snap.net.nz>,
> gdb@sources.redhat.com, Vladimir Prus <ghost@cs.msu.su>
>
> On Fri, Mar 17, 2006 at 01:42:46PM +0200, Eli Zaretskii wrote:
> > > On Thu, Mar 16, 2006 at 03:23:09PM -0800, David Daney wrote:
> > > > I can't see why you would want to do it anyplace *other* than the
> > > > editor. It would know for sure which lines had been added and deleted.
> > > > Anything else would just be guessing.
> > >
> > > Well, in the CLI GDB, we don't have any interaction with the editor.
> >
> > But we can ask the CLI users to type the line difference, can we? I
> > don't expect this command to be used too frequently from the command
> > line, so it doesn't seem to harsh a limitation.
>
> Would that be useful?

I expect it to be used only very rarely from CLI, but when it is, I
think yes, it would be useful.

> The user's rarely going to know "oh, that breakpoint moved twenty
> lines".

If that same user just inserted N lines in the source file, they would
know.

> The alternative command, "oh, that breakpoint should be over here now",
> is a lot simpler for a CLI user to use.

By ``here'' you mean file:line argument? If so, I agree that this is
also a possible user interface that is functionally equivalent to
``move by N lines''.