Essential GDB debugging commands
GDB, the GNU Project debugger, allows you to see what is going on `inside' another program while it executes – or what another program was doing at the moment it crashed.
Essential GDB commands
GDB can do four main kinds of things (plus other things in support of these) to help you catch bugs in the act:
- Start your program, specifying anything that might affect its behavior.
- Make your program stop on specified conditions.
- Examine what has happened, when your program has stopped.
- Change things in your program, so you can experiment with correcting the effects of one bug and go on to learn about another.
The following is a list of most used GDB commands :
| Command | Explanation |
|---|---|
| i b | info breakpoints |
| d n | delete breakpoint n |
| b src.c:line | create breakpoint (bp) in source file |
| step | follow function call |
| next | instruction (without jumping into function calls) |
| run | start the program from the beginning |
| c | continue to next bp |
| d | delete all bp |
| bt | back-trace, shows function call stack with args |
| finish | continue till end of current function |
| until | finish current loop |
| i args | information/values about function arguments |
| Labels: howto, coding |
|
Comment