From 29f5c0388cc5b12a3ddc99cc8434247a8fcfbcc7 Mon Sep 17 00:00:00 2001 From: Stephane Carrez Date: Sun, 1 Sep 2002 08:52:36 +0000 Subject: [PATCH] * gdb.texinfo (TUI Overview): Document breakpoint markers. --- gdb/doc/ChangeLog | 4 ++++ gdb/doc/gdb.texinfo | 33 +++++++++++++++++++++++++++++++-- 2 files changed, 35 insertions(+), 2 deletions(-) diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog index fb133d8abb..2869c98a35 100644 --- a/gdb/doc/ChangeLog +++ b/gdb/doc/ChangeLog @@ -1,5 +1,9 @@ 2002-09-01 Stephane Carrez + * gdb.texinfo (TUI Overview): Document breakpoint markers. + +2002-09-01 Stephane Carrez + * gdb.texinfo (TUI Single Key Mode): Document new SingleKey mode. (TUI Keys): Likewise. diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index 1dc970f26b..ff14bcfd4b 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -13142,8 +13142,6 @@ window is always visible. @item source The source window shows the source file of the program. The current line as well as active breakpoints are displayed in this window. -The current program position is shown with the @samp{>} marker and -active breakpoints are shown with @samp{*} markers. @item assembly The assembly window shows the disassembly output of the program. @@ -13155,6 +13153,37 @@ changed are highlighted. @end table +The source and assembly windows show the current program position +by highlighting the current line and marking them with the @samp{>} marker. +Breakpoints are also indicated with two markers. A first one +indicates the breakpoint type: + +@table @code +@item B +Breakpoint which was hit at least once. + +@item b +Breakpoint which was never hit. + +@item H +Hardware breakpoint which was hit at least once. + +@item h +Hardware breakpoint which was never hit. + +@end table + +The second marker indicates whether the breakpoint is enabled or not: + +@table @code +@item + +Breakpoint is enabled. + +@item - +Breakpoint is disabled. + +@end table + The source, assembly and register windows are attached to the thread and the frame position. They are updated when the current thread changes, when the frame changes or when the program counter changes. -- 2.11.0