comparison man/building.texi @ 66567:1b800330fe1f

(GDB Graphical Interface): Don't reference gdb-mouse-set-clear-breakpoint. Explain gdb-mouse-until must stay in same frame.

66566:c996c096d936

the point of this mode is that you can do it through menus and clicks,
without needing to know GDB commands.  For example, you can click
@kbd{Mouse-1} in the fringe or display margin of a source buffer to
set a breakpoint there and, on a graphical display, a red bullet will
appear.  If a breakpoint already exists on that line, this action will
remove it (@code{gdb-mouse-set-clear-breakpoint}).  You can also
enable or disable a breakpoint by clicking @kbd{Mouse-3} on the
bullet.  If you drag the debugger arrow in the fringe with
@kbd{Mouse-1}, execution will continue to where you release the button
(@code{gdb-mouse-until}).  Alternatively, you can click @kbd{Mouse-2}
at some point in the fringe of this buffer and execution will advance
to there.

@vindex gud-gdb-command-name

66567:1b800330fe1f

the point of this mode is that you can do it through menus and clicks,
without needing to know GDB commands.  For example, you can click
@kbd{Mouse-1} in the fringe or display margin of a source buffer to
set a breakpoint there and, on a graphical display, a red bullet will
appear.  If a breakpoint already exists on that line, this action will
remove it.  You can also enable or disable a breakpoint by clicking
@kbd{Mouse-3} on the bullet.  If you drag the debugger arrow in the
fringe with @kbd{Mouse-1}, execution will continue to the line where
you release the button, provided it is still in the same frame
(@code{gdb-mouse-until}).  Alternatively, you can click @kbd{Mouse-2}
at some point in the fringe of this buffer and execution will advance
to there.

@vindex gud-gdb-command-name