Created attachment 485978 [details] The files from: xorg-x11-server-Xorg-1.10.0-3.fc15.x86_64 + xorg-x11-server-debuginfo-1.10.0-3.fc15.x86_64 Description of problem: addr2line or gdb works in such case. Version-Release number of selected component (if applicable): elfutils-0.152-1.fc15.x86_64 binutils-2.21.51.0.6-1.fc15.x86_64 gdb-7.2.50.20110305-28.fc15.x86_64 xorg-x11-server-Xorg-1.10.0-3.fc15.x86_64 xorg-x11-server-debuginfo-1.10.0-3.fc15.x86_64 How reproducible: Always. Steps to Reproduce: $ eu-addr2line -e /usr/bin/Xorg 0x4a105f Actual results: ??:0 Expected results: /usr/src/debug/xorg-server-1.10.0/os/backtrace.c:46 Additional info: $ gdb -q /usr/bin/Xorg -ex 'info line *0x4a105f' -ex q Line 46 of "backtrace.c" starts at address 0x4a105f <xorg_backtrace+47> and ends at 0x4a1067 <xorg_backtrace+55>. $ eu-addr2line -e /usr/bin/Xorg 0x4a105f ??:0 $ addr2line -e /usr/bin/Xorg 0x4a105f ??:0 $ eu-addr2line -e /usr/lib/debug/usr/bin/Xorg.debug 0x4a105f ??:0 $ addr2line -e /usr/lib/debug/usr/bin/Xorg.debug 0x4a105f /usr/src/debug/xorg-server-1.10.0/os/backtrace.c:46 $ prelink -u -o /tmp/y /usr/bin/Xorg $ eu-unstrip -o /tmp/x /tmp/y /usr/lib/debug/usr/bin/Xorg.debug $ eu-addr2line -e /tmp/x 0x4a105f ??:0 $ addr2line -e /tmp/x 0x4a105f /usr/src/debug/xorg-server-1.10.0/os/backtrace.c:46
Since that eu-unstrip output file apparently reproduces the problem, it would be easiest if you could just attach that one binary to this bug.
Created attachment 486076 [details] xz of /tmp/x (=after eu-unstrip)
This file has no .debug_aranges section. libdw relies on that section. Did the compiler fail to emit one? Or did something else remove it?
Tracked now upstream as a gcc-4.6 regression, thanks for the analysis.