GNU Debugger

GNU Debugger
Developer(s)	GNU Project
Initial release	1986
Stable release	7.4.1 / April 26, 2012; 12 years ago
Repository	sourceware.org/git/binutils-gdb.git ;
Operating system	Unix-like, Windows
Type	Debugger
License	GNU GPL
Website	www.gnu.org/software/gdb

The GNU Debugger, usually called just GDB and named gdb as an executable file, is the standard debugger for the GNU software system.^[vague] It is a portable debugger that runs on many Unix-like systems and works for many programming languages, including Ada, C, C++, Objective-C, Free Pascal, Fortran, Java^[1] and partially others.^[2]

History

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.^[3]

From 1990 to 1993 it was maintained by John Gilmore while he worked for Cygnus Solutions ^{[citation needed]}. Now it is maintained by the GDB Steering Committee which is appointed by the Free Software Foundation.^[4]

Release history

2012 April 26: GDB 7.4.1
2012 January 24: GDB 7.4
2011 July 26: GDB 7.3^[5]
2010 September 2: GDB 7.2
2010 March 18: GDB 7.1
2009 October 6: GDB 7.0
2008 March 27: GDB 6.8
2003 October 3: GDB 6.0

Technical details

Features

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, 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 developed. As of version 7.0 new features include support for Python scripting.^[7] At least since version 7.3, "reversible debugging" ^[8] — allowing a debugging session to step backward, much like rewinding a crashed program to see what happened — has been added.

Remote debugging

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' which understands GDB protocol via Serial or TCP/IP. ^[9] 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.^[10] 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) ^{[citation needed]}.

Graphical user interface

The debugger does not contain its own graphical user interface, and defaults to a command-line interface. Several front-ends have been built for it, such as Xxgdb, Data Display Debugger (DDD), Nemiver, KDbg, Xcode debugger, GDBtk/Insight and the HP Wildebeest Debugger GUI (WDB GUI). IDEs such as Codelite, Code::Blocks, GNAT Programming Studio (GPS), KDevelop, Qt Creator, MonoDevelop, Eclipse, NetBeans and VisualStudio (see VS AddIn Gallery) can interface with GDB. GNU Emacs has a "GUD mode" and several tools for VIM exist^{[citation needed]}. 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.

Examples of commands

`gdb program`	debug "program" (from the shell)
`run -v`	run the loaded program with the parameters
`bt`	backtrace (in case the program crashed)
`info registers`	dump all registers
`disass $pc-32, $pc+32`	disassemble

An example session

Consider the following source-code written in C:

#include <stdio.h>
#include <stdlib.h>
#include <string.h>

size_t
foo_len (const char *s)
{
  return strlen (s);
}

int
main (int argc, char *argv[])
{
  const char *a = NULL;

  printf ("size of a = %d\n", foo_len (a));

  exit (0);
}

Using the GCC compiler on GNU/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:

gcc example.c -g -o example

And the binary can now be run:

# ./example
Segmentation fault

Since the example code, when executed, generates a segmentation fault, GDB can be used to inspect the problem.

# gdb ./example
GNU gdb (GDB) Fedora (7.3.50.20110722-13.fc16)
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /path/example...done.
(gdb) run
Starting program: /path/example 

Program received signal SIGSEGV, Segmentation fault.
0x0000000000400527 in foo_len (s=0x0) at example.c:8
8	  return strlen (s);
(gdb) print s
$1 = 0x0

The problem is present in line 8, and occurs when calling the function strlen (because its argument, s, is NULL).

Depending on the implementation of strlen (in-line or not), the output can be different, eg:

# gdb ./example
GNU gdb (GDB) 7.3.1
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /tmp/gdb/example...done.

(gdb) run
Starting program: /tmp/gdb/example 

Program received signal SIGSEGV, Segmentation fault.
0xb7ee94f3 in strlen () from /lib/i686/cmov/libc.so.6

(gdb) bt
#0  0xb7ee94f3 in strlen () from /lib/i686/cmov/libc.so.6
#1  0x08048435 in foo_len (s=0x0) at example.c:8
#2  0x0804845a in main (argc=<optimized out>, argv=<optimized out>) at example.c:16

To fix the problem, the variable a (in the function main) must contain a valid string. Here is a fixed version of the code:

#include <stdio.h>
#include <stdlib.h>
#include <string.h>

size_t
foo_len (const char *s)
{
  return strlen (s);
}

int
main (int argc, char *argv[])
{
  const char *a = "This is a test string";

  printf ("size of a = %d\n", foo_len (a));

  exit (0);
}

Recompiling and running the executable again inside GDB now gives a correct result:

GNU gdb (GDB) Fedora (7.3.50.20110722-13.fc16)
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /path/example...done.
(gdb) run
Starting program: /path/example 
size of a = 21
[Inferior 1 (process 14290) exited normally]

GDB prints the output of printf in the screen, and then informs the user that the program exited normally.

References

^ "GDB Documentation - Supported Languages". Retrieved 2011-11-28.
^ "GDB Documentation - Summary". Retrieved 2011-11-28.
^ ^a ^b "Richard Stallman lecture at the Royal Institute of Technology, Sweden (1986-10-30)". Retrieved 2006-09-21. Then after GNU Emacs was reasonably stable, which took all in all about a year and a half, I started getting back to other parts of the system. I developed a debugger which I called GDB which is a symbolic debugger for C code, which recently entered distribution. Now this debugger is to a large extent in the spirit of DBX, which is a debugger that comes with Berkeley Unix.
^ "GDB Steering Committee". Retrieved 2008-05-11.
^ http://www.gnu.org/software/gdb/news/
^ "GDB Documentation - Summary - Contributors". Retrieved 2011-12-01.
^ "GDB 7.0 Release Notes". Retrieved 2011-11-28.
^ "GDB 7.3 Documentation - "Running programs backward"". Retrieved 2011-11-28.
^ Howto: GDB Remote Serial Protocol: Writing a RSP Server
^ Implementing a remote stub

External links

Documentation

Richard M. Stallman, Roland Pesch, Stan Shebs, et al., Debugging with GDB (Free Software Foundation, 2011) ISBN 978-0-9831592-3-0
GDB Internals

Tutorials

Peter Jay Salzman's GDB guide: Using The GNU GDB Debugger (Peter Jay Salzman)
RMS's gdb Tutorial (Ryan Schmidt)

[1] "GDB Documentation - Supported Languages". Retrieved 2011-11-28.

[2] "GDB Documentation - Summary". Retrieved 2011-11-28.

[stallman-quote-1986-3] "Richard Stallman lecture at the Royal Institute of Technology, Sweden (1986-10-30)". Retrieved 2006-09-21. Then after GNU Emacs was reasonably stable, which took all in all about a year and a half, I started getting back to other parts of the system. I developed a debugger which I called GDB which is a symbolic debugger for C code, which recently entered distribution. Now this debugger is to a large extent in the spirit of DBX, which is a debugger that comes with Berkeley Unix.

[4] "GDB Steering Committee". Retrieved 2008-05-11.

[5] ttp://www.gnu.org/software/gdb/news/

[6] "GDB Documentation - Summary - Contributors". Retrieved 2011-12-01.

[7] "GDB 7.0 Release Notes". Retrieved 2011-11-28.

[8] "GDB 7.3 Documentation - "Running programs backward"". Retrieved 2011-11-28.

[9] Howto: GDB Remote Serial Protocol: Writing a RSP Server

[10] Implementing a remote stub

[1]

[2]

[3]

[4]

[5]

[6]

[7]

[8]

[9]

[10]

v t e GNU Project
History	GNU Manifesto Free Software Foundation Europe India Latin America History of free software
Licenses	GNU General Public License linking exception font exception GNU Lesser General Public License GNU Affero General Public License GNU Free Documentation License GNAT Modified General Public License
Software	GNU (variants) Hurd Linux-libre glibc Bash coreutils findutils Build system GCC binutils GDB GRUB GNUstep GIMP Jami GNU Emacs GNU TeXmacs GNU Octave GNU Taler GNU R GSL GMP GNU Electric GNU Archimedes GNUnet GNU Privacy Guard Gnuzilla (IceCat) GNU Health GNUmed GNU LilyPond GNU Go GNU Chess Gnash Guix more...
Contributors	Alexandre Oliva Benjamin Mako Hill Bradley M. Kuhn Brian Fox Federico Heinz Georg C. F. Greve John Sullivan Nagarjuna G. Richard M. Stallman
Other topics	GNU/Linux naming controversy Revolution OS Free Software Foundation anti-Windows campaigns Defective by Design