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. How to make gdb to use different directory to look for source files For example my source file during the compilation was in directory Now, when you have source level info go and explore something Resources introduction to the dwarf debugging format gdb doc on source path
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 output gdb offers many more ways to debug and understand your code like examining stack, memory, threads, manipulating the program, etc I hope the above example helps you get started with gdb
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. Learn how to effectively debug c/c++ using gdb on linux Discover key gdb commands like backtrace & frame inspection to resolve core dumps. The source path specifies the directories where the c and c++ source files are located
How do i list breakpoints in gdb?
OPEN
