How to debug using gdb?

by

Here is a quick start tutorial for gdb:

/* test.c  */
/* Sample program to debug.  */
#include <stdio.h>
#include <stdlib.h>

int
main (int argc, char **argv) 
{
  if (argc != 3)
    return 1;
  int a = atoi (argv[1]);
  int b = atoi (argv[2]);
  int c = a + b;
  printf ("%d\n", c);
  return 0;
}

Compile with the -g3 option. g3 includes extra information, such as all the macro definitions present in the program.

gcc -g3 -o test test.c

Load the executable, which now contain the debugging symbols, into gdb:

gdb --annotate=3 test.exe

Now you should find yourself at the gdb prompt. There you can issue commands to gdb.
Say you like to place a breakpoint at line 11 and step through the execution, printing the values of the local variables – the following commands sequences will help you do this:

(gdb) break test.c:11
Breakpoint 1 at 0x401329: file test.c, line 11.
(gdb) set args 10 20
(gdb) run
Starting program: c:\Documents and Settings\VMathew\Desktop/test.exe 10 20
[New thread 3824.0x8e8]

Breakpoint 1, main (argc=3, argv=0x3d5a90) at test.c:11
(gdb) n
(gdb) print a
$1 = 10
(gdb) n
(gdb) print b
$2 = 20
(gdb) n
(gdb) print c
$3 = 30
(gdb) c
Continuing.
30

Program exited normally.
(gdb)

In short, the following commands are all you need to get started using gdb:

break file:lineno - sets a breakpoint in the file at lineno.
set args - sets the command line arguments.
run - executes the debugged program with the given command line arguments.
next (n) and step (s) - step program and step program until it 
                        reaches a different source line, respectively. 
print - prints a local variable
bt -  print backtrace of all stack frames
c - continue execution.

Type help at the (gdb) prompt to get a list and description of all valid commands.

More Related Contents:

  1. Best way to invoke gdb from inside program to print its stacktrace?
  2. How can I tell if a library was compiled with -g?
  3. How to print every executed line in GDB automatically until a given breakpoint is reached?
  4. Include source code of malloc.c in gdb?
  5. Is it possible to “jump”/”skip” in GDB debugger?
  6. gdb – debugging with pipe
  7. Printing all global variables/local variables?
  8. How to solve “ptrace operation not permitted” when trying to attach GDB to a process?
  9. Cannot insert breakpoints. Addresses with low values
  10. Why does gdb evaluate sqrt(3) to 0?
  11. How do I pass a command line argument while starting up GDB in Linux? [duplicate]
  12. How to modify memory contents using GDB?
  13. segfault only when NOT using debugger
  14. How do I print a #defined constant in GDB?
  15. How do I debug the child process after fork() in gdb?
  16. Can’t step into string.h function with GDB
  17. gdb gives strange output when using math.h functions [duplicate]
  18. Why GDB jumps unpredictably between lines and prints variables as “”?
  19. How to do an specific action when a certain breakpoint is hit in GDB?
  20. Program received signal SIGPIPE, Broken pipe
  21. Recommended way to track down array out-of-bound access/write in C program
  22. gdb prints wrong values when modifying arguments
  23. What exactly is -fno-builtin doing here?
  24. Debugging child process after fork (follow-fork-mode child configured)
  25. Which ordering of nested loops for iterating over a 2D array is more efficient [duplicate]
  26. malloc implementation?
  27. No loop condition in for and while loop
  28. Socketpair() in C/Unix
  29. Getting max value in a __m128i vector with SSE?
  30. Does Microsoft visual studio 2010 support c99?

Leave a Comment