The source path will always include two special entries ‘$cdir’ and ‘$cwd’, these refer to the compilation directory (if one is recorded) and the current working directory respectively. ‘$cdir’ causes GDB to search within the compilation directory, if one is recorded in the debug information.

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.

April 30, 2017 - To find the sources GDB parses .debug_info section to find all DIEs with tag DW_TAG_compile_unit. The DIE with this tag has 2 main attributes DW_AT_comp_dir (compilation directory) and DW_AT_name - path to the source file.

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. For example, suppose an executable references the file `/usr/src/foo-1.0/lib/foo.c', and our source path is `/mnt/cross'.

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 ...

November 21, 2016 - The Eclipse Foundation - home to a global community, the Eclipse IDE, Jakarta EE and over 350 open source projects, including runtimes, tools and frameworks.

The set substitute-path command tells the debugger where to find the sources, so the list command displays the source code:

January 13, 2015 - While debugging, clicking on a stack frame opens a source code file. Let's say the file is /apps/home/martin/my-project/my-file.cpp. CLion does not seem to recognize this as the project file because it tracks it as ~/my-project/my-file.cpp. We have a symbolic link as follows: ln -s /apps/home/martin /home/martin It seems the symbolic link on the path prevents the IDE to recognize that the files are the same.

April 18, 2022 - The window displays the path of the currently debugged executable (1), and the exact path reported by gdb (2) and allows recursively searching an arbitrary directory (3) for the files with the matching name.

May 9, 2024 - I need debuginfo for some libraries, for example gstreamer (which are not available in debian repo), but can be built using source packages. However it turns out that the source paths in the debug info is something like ../gst/gsttask.c that is relative to the build-dir. I could perhaps point out the build dir in gdb, but if I do this with a few libraries it becomes a bit unpractical.

March 9, 2022 - I suggest to add a sourceFileMap setting. This would need to applied anywhere the client passes paths (breakpoints, "go to cursor") and when the client receives paths (I guess that's the stack only). ... People are using their own gdb-init scripts to [do path substitutions] - No help from extension needed.

April 13, 2017 - { "version": "0.2.0", "configurations": [ { "name": "(gdb) remote debug", "type": "cppdbg", "request": "launch", "program": "${workspaceRoot}/build/bin/app", "debugServerArgs": "dir ${workspaceRoot}/src", "stopAtEntry": false, "cwd": "${workspaceRoot}", "environment": [], "externalConsole": true, "MIMode": "gdb", "miDebuggerServerAddress": "localhost:2222", "setupCommands": [ { "description": "Enable pretty-printing for gdb", "text": "-enable-pretty-printing", "ignoreFailures": true } ] } ] }

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 ...

February 2, 2007 - When I debug my project with GDB I'm able to stop at breakpoints in the main program but not at ones set in the library its linked against. When using GDB from the command line I can supply the -d /ad...

Improvements can be sent to [email protected].