Commits on Source (2)
-
When GDB looks for debug symbols it looks for the full path of the file inside the configured debug-file-directory. For example, if the debug-file-directory is set to a default of /usr/lib/debug, and you are debugging /usr/bin/python3, GDB will look for its debug symbols at this location: /usr/lib/debug/usr/bin/python3. BuildStream has been putting all debug files inside /usr/lib/debug under their $(basename), so in the above example GDB would fail to find any debug symbols for /usr/bin/python3 because they would be in the incorrect locatoin of /usr/lib/debug/python3.
-
Tristan Van Berkom authored
Don't strip pathname from debug symbol files See merge request !698
Showing
- buildstream/data/projectconfig.yaml 2 additions, 2 deletionsbuildstream/data/projectconfig.yaml
- tests/cachekey/project/elements/build1.expected 1 addition, 1 deletiontests/cachekey/project/elements/build1.expected
- tests/cachekey/project/elements/build2.expected 1 addition, 1 deletiontests/cachekey/project/elements/build2.expected
- tests/cachekey/project/target.expected 1 addition, 1 deletiontests/cachekey/project/target.expected
- tests/examples/autotools.py 3 additions, 1 deletiontests/examples/autotools.py
- tests/examples/flatpak-autotools.py 4 additions, 2 deletionstests/examples/flatpak-autotools.py
- tests/integration/autotools.py 4 additions, 2 deletionstests/integration/autotools.py
- tests/integration/cmake.py 3 additions, 1 deletiontests/integration/cmake.py
- tests/integration/compose.py 10 additions, 4 deletionstests/integration/compose.py