Set or clear a breakpoint on that line
Enable or disable a breakpoint on that line
Continue execution to that line (
Jump to that line (
On a graphical display, you can click mouse-1 in the fringe of a source buffer, to set a breakpoint on that line (see Window Fringes). A red dot appears in the fringe, where you clicked. If a breakpoint already exists there, the click removes it. A C-mouse-1 click enables or disables an existing breakpoint; a breakpoint that is disabled, but not unset, is indicated by a gray dot.
On a text terminal, or when fringes are disabled, enabled breakpoints are indicated with a ‘B’ character in the left margin of the window. Disabled breakpoints are indicated with ‘b’. (The margin is only displayed if a breakpoint is present.)
A solid arrow in the left fringe of a source buffer indicates the line of the innermost frame where the debugged program has stopped. A hollow arrow indicates the current execution line of a higher-level frame. If you drag the arrow in the fringe with mouse-1, that causes execution to advance to the line where you release the button. Alternatively, you can click mouse-3 in the fringe to advance to that line. You can click C-mouse-3 in the fringe to jump to that line without executing the intermediate lines. This command allows you to go backwards, which can be useful for running through code that has already executed, in order to examine its execution in more detail.
By default, source file names and non-ASCII strings in the program
being debugged are decoded using the default coding-system. If you
prefer a different decoding, perhaps because the program being
debugged uses a different character encoding, set the variable
gdb-mi-decode-strings to the appropriate coding-system, or to
nil to leave non-ASCII characters as undecoded octal escapes.