| Developer: | GNU Project |
| Programming Language: | C, C++, Python |
| Operating System: | Unix-like, Windows |
| Genre: | Debugger |
| License: | GPLv3 |
The GNU Debugger (GDB) is a portable debugger that runs on many Unix-like systems and works for many programming languages, including Ada, Assembly, C, C++, D, Fortran, Haskell, Go, Objective-C, OpenCL C, Modula-2, Pascal, Rust,[1] and partially others.[2]
GDB was first written by Richard Stallman in 1986 as part of his GNU system, after his GNU Emacs was "reasonably stable".[3] GDB is free software released under the GNU General Public License (GPL). It was modeled after the DBX debugger, which came with Berkeley Unix distributions.
From 1990 to 1993 it was maintained by John Gilmore.[4] Now it is maintained by the GDB Steering Committee which is appointed by the Free Software Foundation.[5]
GDB offers extensive facilities for tracing and altering the execution of computer programs. The user can monitor and modify the values of programs' internal variables, and even call functions independently of the program's normal behavior.
GDB target processors (as of 2003) include: Alpha, ARM, AVR, H8/300, Altera Nios/Nios II, System/370, System 390, X86 and its 64-bit extension X86-64, IA-64 "Itanium", Motorola 68000, MIPS, PA-RISC, PowerPC, SuperH, SPARC, and VAX. Lesser-known target processors supported in the standard release have included A29K, ARC, ETRAX CRIS, D10V, D30V, FR-30, FR-V, Intel i960, 68HC11, Motorola 88000, MCORE, MN10200, MN10300, NS32K, Stormy16, and Z8000. (Newer releases will likely not support some of these.) GDB has compiled-in simulators for even lesser-known target processors such like M32R or V850.[6]
GDB is still actively being developed. As of version 7.0 new features include support for Python scripting[7] and as of version 7.8 GNU Guile scripting as well.[8] Since version 7.0, support for "reversible debugging" — allowing a debugging session to step backward, much like rewinding a crashed program to see what happened — is available.[9]
GDB offers a "remote" mode often used when debugging embedded systems. Remote operation is when GDB runs on one machine and the program being debugged runs on another. GDB can communicate to the remote "stub" that understands GDB protocol through a serial device or TCP/IP.[10] A stub program can be created by linking to the appropriate stub files provided with GDB, which implement the target side of the communication protocol.[11] Alternatively, gdbserver can be used to remotely debug the program without needing to change it in any way.
The same mode is also used by KGDB for debugging a running Linux kernel on the source level with gdb. With KGDB, kernel developers can debug a kernel in much the same way as they debug application programs. It makes it possible to place breakpoints in kernel code, step through the code, and observe variables. On architectures where hardware debugging registers are available, watchpoints can be set which trigger breakpoints when specified memory addresses are executed or accessed. KGDB requires an additional machine which is connected to the machine to be debugged using a serial cable or Ethernet. On FreeBSD, it is also possible to debug using FireWire direct memory access (DMA).[12]
The debugger does not contain its own graphical user interface, and defaults to a command-line interface, although it does contain a text user interface. Several front-ends have been built for it, such as UltraGDB, Xxgdb, Data Display Debugger (DDD), Nemiver, KDbg, the Xcode debugger, GDBtk/Insight, Seer, and HP Wildebeest Debugger GUI (WDB GUI). IDEs such as Codelite,, Dev-C++, Geany, GNAT Programming Studio (GPS), KDevelop, Qt Creator, Lazarus, MonoDevelop, Eclipse, NetBeans, and Visual Studio can interface with GDB. GNU Emacs has a "GUD mode" and tools for Vim exist (e.g. clewn). These offer facilities similar to debuggers found in IDEs.
Some other debugging tools have been designed to work with GDB, such as memory leak detectors.
GDB uses a system call named ptrace (the name is an abbreviation of "process trace") to observe and control the execution of another process, and examine and change the process' memory and registers.A breakpoint is implemented by replacing an instruction at a given memory address with another special instruction. Executing breakpoint instruction causes SIGTRAP.
| Debug "program" (from the shell) | ||
| Run the loaded program with the parameters | ||
| Backtrace (in case the program crashed) | ||
| Dump all registers | ||
| Disassemble |
Consider the following source-code written in C:
size_t foo_len(const char *s)
int main(int argc, char *argv[])
Using the GCC compiler on Linux, the code above must be compiled using the -g flag in order to include appropriate debug information on the binary generated, thus making it possible to inspect it using GDB. Assuming that the file containing the code above is named example.c, the command for the compilation could be:
Since the example code, when executed, generates a segmentation fault, GDB can be used to inspect the problem.
Program received signal SIGSEGV, Segmentation fault.0x0000000000400527 in foo_len (s=0x0) at example.c:77 return strlen (s);(gdb) print s$1 = 0x0
The problem is present in line 7, and occurs when calling the function [[Strlen#strlen|strlen]] (because its argument, s, is [[Null pointer#Null pointer|NULL]]).Depending on the implementation of strlen (inline or not), the output can be different, e.g.:
Program received signal SIGSEGV, Segmentation fault.0xb7ee94f3 in strlen from /lib/i686/cmov/libc.so.6(gdb) bt
To fix the problem, the variable a (in the function main) must contain a valid string. Here is a fixed version of the code:
size_t foo_len(const char *s)
int main(int argc, char *argv[])
Recompiling and running the executable again inside GDB now gives a correct result:printf in the screen, and then informs the user that the program exited normally.