on, forces GDB to assume that GDB was started
in a terminal. In practice, this means that GDB should wait
for the user to answer queries generated by commands entered at
the command prompt. If
off, forces GDB to operate
in the opposite mode, and it uses the default answers to all queries.
auto (the default), GDB tries to determine whether
its standard input is a terminal, and works in interactive-mode if it
is, non-interactively otherwise.
In the vast majority of cases, the debugger should be able to guess correctly which mode should be used. But this setting can be useful in certain specific cases, such as running a MinGW GDB inside a cygwin window.
Displays whether the debugger is operating in interactive mode or not.
on, command-line-interface (CLI) notifications that are
printed by GDB are suppressed. If
notifications are printed as usual. The default value is
CLI notifications occur when you change the selected context or when
the program being debugged stops, as detailed below.
When you change the selected context (i.e. the current inferior, thread and/or the frame), GDB prints information about the new context. For example, the default behavior is below:
(gdb) inferior 1 [Switching to inferior 1 [process 634] (/tmp/test)] [Switching to thread 1 (process 634)] #0 main () at test.c:3 3 return 0; (gdb)
When the notifications are suppressed, the new context is not printed:
(gdb) set suppress-cli-notifications on (gdb) inferior 1 (gdb)
When the program you are debugging stops (e.g. because of hitting a breakpoint, completing source-stepping, an interrupt, etc.), GDB prints information about the stop event. For example, below is a breakpoint hit:
(gdb) break test.c:3 Breakpoint 2 at 0x555555555155: file test.c, line 3. (gdb) continue Continuing. Breakpoint 2, main () at test.c:3 3 return 0; (gdb)
When the notifications are suppressed, the output becomes:
(gdb) break test.c:3 Breakpoint 2 at 0x555555555155: file test.c, line 3. (gdb) set suppress-cli-notifications on (gdb) continue Continuing. (gdb)
Suppressing CLI notifications may be useful in scripts to obtain a reduced output from a list of commands.
Displays whether printing CLI notifications is suppressed or not.