Jkinne: 1 revision imported

2025-08-17T13:22:16Z

1 revision imported

← Older revision		Revision as of 13:22, 17 August 2025
(No difference)

wiki_previous>Jkinne: /* gdb Commands */

2024-01-31T13:21:03Z

gdb Commands

New page

This page has information to get you started with the GNU Debugger, which is the <code>gdb</code> command on the server.

=Compiling and Starting gdb=
To run a C program in the GNU Debugger, you use the <code>gdb</code> command. First you need to compile the file with the <code>-g</code> flag so that it contains debugging information. We use the file [https://cs.indstate.edu/learn/C/fix_errors/args_add4.c args_add4.c] as an example. You can download this file, or you can copy/paste the code into a text editor and save it as args_add4.c. When debugging and testing code, it is also a good idea to turn on all warnings (with the <code>-Wall</code> option) and turn off compiler optimization (with the <code>-O0</code> option).

To compile with debugging information, you run:
<pre>gcc -g -Wall -O0 args_add4.c -o args_add4.o</pre>

To run the program in <code>gdb</code>, you run <code>gdb</code> giving the .o file name as a parameter:
<pre>gdb args_add4.o</pre>
This has loaded the program into the debugger.

=Commands in gdb=
The rest of this article is assuming you have started <code>gdb</code> as indicated above. You interact with <code>gdb</code> by typing commands after you have started the program.

To run the program you use the ''run'' command and give any command-line arguments after run. For example:
<pre>run 1 2 3</pre>

When you type enter, the program will run. If it crashes, the debugger stops the program from crashing so you can take a look at what is happening. When we run the above, we see the following.
<pre>
(gdb) run 1 2 3
Starting program: /net/web/learn/C/fix_errors/args_add4.o 1 2 3

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7de5633 in ____strtod_l_internal () from /lib64/libc.so.6
(gdb)
</pre>
There has been a segmentation fault. We can see information about the status of the program by typing the ''backtrace'' command:
<pre>
(gdb) backtrace
#0 0x00007ffff7de5633 in ____strtod_l_internal () from /lib64/libc.so.6
#1 0x0000000000401174 in main (argc=4, argv=0x7fffffffdfa8) at args_add4.c:15
(gdb)
</pre>
The problem is at line 15 in the program. We can see what is at line 15 either by looking at the file in our text editor, or using the ''list'' command in <code>gdb</code>.
<pre>
(gdb) list 15
10 #include <stdlib.h>
11
12 int main(int argc, char *argv[]) {
13 float total = 0;
14 for(int i=1; i < argc; i--) {
15 total += atof(argv[i]);
16 }
17 printf("%f\n", total);
18
19 return 0;
(gdb)
</pre>
Probably the segmentation fault is the <code>argv[i]</code> on line 15. We can see what the value of ''i'' is by setting the debugger to be using the "stack frame" that has this value (frame #1 as indicated on the output after we ran the ''backtrace'' command) and then using the ''print'' command.
<pre>
(gdb) frame 1
#1 0x0000000000401174 in main (argc=4, argv=0x7fffffffdfa8) at args_add4.c:15
15 total += atof(argv[i]);
(gdb) print i
$1 = -1
(gdb)
</pre>
This is definitely a problem - the index ''i'' should not be negative if we are using it as an array index. Looking back at the printout of the code, the mistake is in line 14: rather than <code>i--</code>, the loop increment should be <code>i++</code>.

=gdb Commands=
The following are a few key commands to get you started in <code>gdb</code>.
* <code>run arg1 arg2 ...</code> (can be abbreviated as <code>r</code>) - run the program that is being debugged, giving it command-line arguments <code>arg1 arg2 ...</code>
* <code>backtrace</code> (can be abbreviated <code>bt</code>) - print a trace of the stack frame, which is a history of which functions have been called and still haven't completed
* <code>frame i</code> (can be abbreviated <code>f</code>) - set the debugger to be using the given (<code>i</code>) stack frame
* <code>print expr</code> (can be abbreviated <code>p</code>) - evaluate the given expression and print its value (e.g., can be used to print the value of a variable)
* <code>quit</code> (can be abbreviated <code>q</code>) - quit the debugger
* <code>(s)tep</code> - step one line at a time (going into a function if the next line is a function call).
* <code>(c)ontinue</code> - continue execution.
* <code>break file_name.c:100</code> - set a break point at line 100 in file_name.c
* <code>break function_name</code> - set a break point on function_name.

For more information, search online for GDB tutorials, reference sheets, and documentation. The official documentation is here - https://www.sourceware.org/gdb/documentation/ A good quick start is https://web.eecs.umich.edu/~sugih/pointers/gdbQS.html

GNU Debugger - Revision history

Jkinne: 1 revision imported

wiki_previous>Jkinne: /* gdb Commands */