GDB (GNU DeBugger) allows you to step through the execution of a program in order to find the point at which it breaks. It fully supports C and C++, and provides partial support for FORTRAN, Java, Chill, assembly, and Modula-2. The program to be debugged is normally specified on the command line; you can also specify a core or, if you want to investigate a running program, a process ID.
Set line speed of serial device used by GDB to bps.
Exit after executing all the commands specified in .gdbinit and -x files. Print no startup messages.
Consult file for information provided by a core dump.
Use directory as gdb’s working directory.
Include directory in path that is searched for source files.
Use file as an executable to be read in conjunction with source code. May be used in conjunction with -s to read the symbol table from the executable.
Show full filename and line number for each stack frame.
Print help message, then exit.
Ignore .gdbinit file.
Suppress introductory and copyright messages.
Consult file for symbol table. With -e, also uses file as the executable.
Set standard in and standard out to device.
Allow gdb to write into executables and core files.
Read gdb commands from file.
These are ...