Using splitdebug, debug information for libraries sometimes appears in /usr/lib/debug/usr/lib/, and sometimes in /usr/lib/debug/usr/lib64/. gdb looks in one of those directories, but not both. The issue can be fixed with: mv /usr/lib/debug/usr/lib64 /usr/lib/debug/usr/lib64_temp ln -s lib /usr/lib/debug/usr/lib64 mv /usr/lib/debug/usr/lib64_temp/* /usr/lib/debug/usr/lib64/ rmdir /usr/lib/debug/usr/lib64_temp I think, either portage should create the symlink automatically, or the backtraces documentation should be updated. Reproducible: Always Steps to Reproduce:
(In reply to comment #0) > Using splitdebug, debug information for libraries sometimes appears in > /usr/lib/debug/usr/lib/, and sometimes in /usr/lib/debug/usr/lib64/. My first guess is that the ones that install in /usr/lib aren't using $(get_libdir) from multilib.eclass. That would be a bug in the ebuild.
yeah, please post real info (like which packages are installing there). native binaries (i.e. 64bit ones) should not be installing into /usr/lib/. those packages are broken and need fixing.
*** Bug 378537 has been marked as a duplicate of this bug. ***
