|
- Source Path (Debugging with GDB) - sourceware. org
In addition to the source path, GDB provides a set of commands that manage a list of source path substitution rules A substitution rule specifies how to rewrite source directories stored in the program’s debug information in case the sources were moved to a different directory between compilation and debugging
- debugging - GDB source path - Stack Overflow
If I there will be a lot such files, adding the whole path for each file is like putting all the files in one debug directory In other words, if you have files with the same names but different directories (during the compilation time) adding the whole paths will cause name conflicts (gdb will not distinguish between this files)
- Debugging with GDB - Examining Source Files
Add directory dirname to the front of the source path Several directory names may be given to this command, separated by `:' or whitespace You may specify a directory that is already in the source path; this moves it forward, so GDB searches it sooner
- Debugging with GDB - Source Path - GNU
Whenever you reset or rearrange the source path, GDB clears out any information it has cached about where source files are found and where each line is in the file When you start GDB, its source path includes only `cdir' and `cwd', in that order To add other directories, use the directory command
- How to point GDB to your sources | There is no magic here
There are multiple ways to help GDB find sources, where the easiest ones are directory and set substitute-path commands, though -fdebug-prefix-map is really useful Now, when you have source level info go and explore something! Resources Introduction to the DWARF Debugging Format GDB doc on source path
- Debugging with GDB: Source
GDB has a list of directories to search for source files; this is called the source path Each time GDB wants a source file, it tries all the directories in the list, in the order they are present in the list, until it finds a file with the desired name Note that the executable search path is not used for this purpose
- Debugging with GDB: Source Path - fifi. org
Neither is the current working directory, unless it happens to be in the source path If GDB cannot find a source file in the source path, and the object program records a directory, GDB tries that directory too If the source path is empty, and there is no record of the compilation directory, GDB looks in the current directory as a last resort
- Find the path of the source code for the executable being . . .
I can set a breakpoint in main and debug the code with the correct source code, but I don't know where GDB is taking the source code from The source code is not present in CWD (current working directory)
|
|
|