https://sourceware.org/bugzilla/show_bug.cgi?id=26043
--- Comment #8 from Mark Wielaard <mark at klomp dot org> --- (In reply to devel.origin from comment #7) > For that demo the debug files are ending up in a custom directory (the > build-id-demo/.build-id/) for the packge builder to pick up. So they can't > be found by GDB. When packages are installed the debug info is naturally in > /usr/lib/debug. > > To make the GDB work when launching a developer build from the build > directory the build script puts a copy of debug info of all libraries into > one .build-id/ on the top level of the build directory (I haven't added this > part to the testcase project). In .gdbinit there is an option to look in > current dir: "set debug-file-directory /usr/lib/debug:.", so GDB finds debug > files if the current dir has a .build-id/ subdir. Thanks. I have a clear picture now. I think it would make sense to change the search for .build-id based files in the default search from only checking absolute paths to also include relative paths. I am just pondering how to prevent an "explosion" of extra stats/checks. With the default setting it would add 2 extra stat calls (which would normally always fail). Maybe that isn't too bad? -- You are receiving this mail because: You are on the CC list for the bug.
