A command file for GDB is a text ... it does not mean to repeat the last command, as it would from the terminal. You can request the execution of a command file with the source command....

<< std::endl; (gdb) info source Current source file is test.cpp Compilation directory is /home/bazis Located in /home/bazis/test.cpp Contains 7 lines. Source language is c++. Compiled with DWARF 2 debugging format. Does not include preprocessor macro info. You can execute the info source command ...

Using the previous example, suppose the foo-1.0 tree has been moved from /usr/src to /mnt/cross, then you can tell GDB to replace /usr/src in all source path names with /mnt/cross. The first lookup will then be /mnt/cross/foo-1.0/lib/foo.c in place of the original location of /usr/src/foo-1.0/lib/foo.c. To define a source path substitution rule, use the set substitute-path command (see set substitute-path).

You can direct GDB to the new source path right in the debug session with directory <dir> command:

When you start GDB, its source path includes only `cdir' and `cwd', in that order. To add other directories, use the directory command.

EDITOR=/usr/bin/vi export EDITOR gdb ... ... There are two commands for searching through the current source file for a regular expression.

Starting program: /home/bazis/test Temporary breakpoint 1, main (argc=1, argv=0xbffff064) at test.cpp:5 5 std::cout << "Hello!" << std::endl; (gdb) info sources Source files for which symbols have been read in: /home/bazis/test.cpp, /home/bazis/<built-in>, /usr/include/wctype.h, /usr/include/i386-linux-gnu/c++/4.8/bits/atomic_word.h, ...

When your program stops, GDB spontaneously prints the line where it stopped. Likewise, when you select a stack frame (see Selecting a Frame), GDB prints the line where execution in that frame has stopped. You can print other portions of source files by explicit command.

July 4, 2023 - Hey, I have external source directories of my library that I want to add to gdb while debugging. In the command line I can do that by calling gdb via gdb --directory=/path/to/sources or by writing directory /path/to/sources while running gdb.

You can abbreviate this command as rev. Executable programs sometimes do not record the directories of the source files from which they were compiled, just the names. Even when they do, the directories could be moved between the compilation and your debugging session. GDB has a list of directories to search for source files; this is called the source path.

A command file for GDB is a text file made of lines that are GDB commands. Comments (lines starting with #) may also be included. An empty line in a command file does nothing; it does not mean to repeat the last command, as it would from the terminal. You can request the execution of a command file with the source command:

Type "apropos word" to search for commands related to "word"... Reading symbols from fibonacci...done. (gdb) Copy to Clipboard Copied! ... Copy to Clipboard Copied! ... Before you start the execution of the program you are debugging, gdb displays the first ten lines of the source code, and any subsequent use of this command lists another ten lines.

March 19, 2022 - This is a huge improvement to using list to actually see what code are you debugging! ... Hit Ctrl + X + 2 and you will get multiple windows: source code, assembly code, registers etc.

An empty line in a command file does nothing; it does not mean to repeat the last command, as it would from the terminal. When you start GDB, it automatically executes commands from its init files. These are files named `.gdbinit' on Unix and `gdb.ini' on DOS/Windows.