From 4cf716044edade7b22a5b9c863dc736ed6ec3601 Mon Sep 17 00:00:00 2001 From: Nick Roberts Date: Sun, 30 Oct 2005 22:16:46 +0000 Subject: [PATCH] (GDB Graphical Interface): Don't reference gdb-mouse-set-clear-breakpoint. Explain gdb-mouse-until must stay in same frame. --- man/building.texi | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/man/building.texi b/man/building.texi index c227fcddd6d..451df233b06 100644 --- a/man/building.texi +++ b/man/building.texi @@ -758,10 +758,10 @@ 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 +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. -- 2.39.5