darkkirb/old-cross-binutils
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

* gdb.texinfo (TUI Overview): Document breakpoint markers.

Browse source
This commit is contained in:
Stephane Carrez 2002-09-01 08:52:36 +00:00
parent 7cf36c7860
commit 269c21feac
2 changed files with 35 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
gdb/doc/ChangeLog
View file

@ -1,3 +1,7 @@
2002-09-01 Stephane Carrez <stcarrez@nerim.fr>
* gdb.texinfo (TUI Overview): Document breakpoint markers.
2002-09-01 Stephane Carrez <stcarrez@nerim.fr>
* gdb.texinfo (TUI Single Key Mode): Document new SingleKey mode.

33
gdb/doc/gdb.texinfo
View file

@ -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.