Bug 293361

Summary:	gdb doesn't display debug information of some libraries, when using splitdebug
Product:	Gentoo Linux	Reporter:	Cyp <cyp561>
Component:	[OLD] Unspecified	Assignee:	Gentoo Toolchain Maintainers <toolchain>
Status:	RESOLVED NEEDINFO
Severity:	normal	CC:	dev-portage, mgorny
Priority:	High
Version:	unspecified
Hardware:	AMD64
OS:	Linux
URL:	http://www.gentoo.org/proj/en/qa/backtraces.xml
Whiteboard:
Package list:		Runtime testing required:	---

Description Cyp 2009-11-16 09:25:51 UTC

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:

Comment 1 Zac Medico gentoo-dev

2009-11-16 20:34:16 UTC

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

Comment 2 SpanKY gentoo-dev

2009-11-16 22:12:14 UTC

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.

Comment 3 Ryan Hill (RETIRED) gentoo-dev

2011-08-10 00:41:43 UTC

*** Bug 378537 has been marked as a duplicate of this bug. ***