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
set verbose off
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).
By default, gdb is cautious, and asks what sometimes seems to be a lot of stupid questions to confirm certain commands. For example, if you try to run a program which is already running:
(gdb) run The program being debugged has been started already. Start it from the beginning? (y or n)
If you are willing to unflinchingly face the consequences of your own commands, you can disable this “feature”:
set confirm off
set confirm on
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
set trace-commands off