22.7 Optional Warnings and Messages
By default, gdb is silent about its inner workings. If you are
running on a slow machine, you may want to use the
command. This makes gdb tell you when it does a lengthy
internal operation, so you will not think it has crashed.
Currently, the messages controlled by
set verbose are those
which announce that the symbol table for a source file is being read;
symbol-file in Commands to Specify Files.
set verbose on
- Enables gdb output of certain informational messages.
set verbose off
- Disables gdb output of certain informational messages.
- Displays whether
set verboseis on or off.
By default, if gdb encounters bugs in the symbol table of an object file, it is silent; but if you are debugging a compiler, you may find this information useful (see Errors Reading Symbol Files).
- Permits gdb to output limit complaints about each type of unusual symbols before becoming silent about the problem. Set limit to zero to suppress all complaints; set it to a large number to prevent complaints from being suppressed.
- Displays how many symbol complaints gdb is permitted to produce.
(gdb) run The program being debugged has been started already. Start it from the beginning? (y or n)
set confirm off
- Disables confirmation requests. Note that running gdb with
the --batch option (see -batch) also
automatically disables confirmation requests.
set confirm on
- Enables confirmation requests (the default).
- Displays state of confirmation requests.
If you need to debug user-defined commands or sourced files you may find it useful to enable command tracing. In this mode each command will be printed as it is executed, prefixed with one or more + symbols, the quantity denoting the call depth of each command.
set trace-commands on
- Enable command tracing.
set trace-commands off
- Disable command tracing.
- Display the current state of command tracing.