25.1 TUI Overview
In TUI mode, gdb can display several text windows:
- This window is the gdb command window with the gdb
prompt and the gdb output. The gdb input is still
managed using readline.
- The source window shows the source file of the program. The current
line and active breakpoints are displayed in this window.
- The assembly window shows the disassembly output of the program.
- This window shows the processor registers. Registers are highlighted
when their values change.
The source and assembly windows show the current program position
by highlighting the current line and marking it with a ‘>’ marker.
Breakpoints are indicated with two markers. The first marker
indicates the breakpoint type:
- Breakpoint which was hit at least once.
- Breakpoint which was never hit.
- Hardware breakpoint which was hit at least once.
- Hardware breakpoint which was never hit.
The second marker indicates whether the breakpoint is enabled or not:
- Breakpoint is enabled.
- Breakpoint is disabled.
The source, assembly and register windows are updated when the current
thread changes, when the frame changes, or when the program counter
These windows are not all visible at the same time. The command
window is always visible. The others can be arranged in several
- source only,
- assembly only,
- source and assembly,
- source and registers, or
- assembly and registers.
A status line above the command window shows the following information:
- Indicates the current gdb target.
(see Specifying a Debugging Target).
- Gives the current process or thread number.
When no process is being debugged, this field is set to
- Gives the current function name for the selected frame.
The name is demangled if demangling is turned on (see Print Settings).
When there is no symbol corresponding to the current program counter,
?? is displayed.
- Indicates the current line number for the selected frame.
When the current line number is not known, the string
?? is displayed.
- Indicates the current program counter address.