bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug binutils/26595] objdump/readelf debuginfod client not invoked for a


From: woodard at redhat dot com
Subject: [Bug binutils/26595] objdump/readelf debuginfod client not invoked for altdebug dwz file
Date: Thu, 10 Sep 2020 21:39:42 +0000

https://sourceware.org/bugzilla/show_bug.cgi?id=26595

--- Comment #3 from Ben Woodard <woodard at redhat dot com> ---
Nick I may be doing something wrong but I'm not able to reproduce fche's
success. It appears like it is following those links which is good but it
doesn't appear to be successfully using them:

Latest trunk with your patch:

$ ~/bin/objdump  --dwarf=loc,follow-links /lib64/libboost_system.so.1.69.0 
/lib64/libboost_system.so.1.69.0: Found separate debug info file:
/usr/lib/debug//usr/lib64//libboost_system.so.1.69.0-1.69.0-18.fc32.x86_64.debug

/usr/lib/debug//usr/lib64//libboost_system.so.1.69.0-1.69.0-18.fc32.x86_64.debug:
Found separate debug info file:
/usr/lib/debug/usr/lib64/../../.dwz/boost-1.69.0-18.fc32.x86_64


/usr/lib/debug/usr/lib64/../../.dwz/boost-1.69.0-18.fc32.x86_64:     file
format elf64-x86-64


/usr/lib/debug//usr/lib64//libboost_system.so.1.69.0-1.69.0-18.fc32.x86_64.debug:
    file format elf64-x86-64


/lib64/libboost_system.so.1.69.0:     file format elf64-x86-64

vs standard fedora32 version of objdump:

$ objdump  --dwarf=loc --dwarf=follow-links /lib64/libboost_system.so.1.69.0 
/lib64/libboost_system.so.1.69.0: Found separate debug info file:
/usr/lib/debug//usr/lib64//libboost_system.so.1.69.0-1.69.0-18.fc32.x86_64.debug


/usr/lib/debug//usr/lib64//libboost_system.so.1.69.0-1.69.0-18.fc32.x86_64.debug:
    file format elf64-x86-64


/lib64/libboost_system.so.1.69.0:     file format elf64-x86-64

To make it clearer:

$ objdump  --dwarf=loc --dwarf=follow-links /lib64/libboost_system.so.1.69.0 >
foo
$ ~/bin/objdump  --dwarf=loc --dwarf=follow-links
/lib64/libboost_system.so.1.69.0 > bar
$ diff -u foo bar 
--- foo 2020-09-10 14:37:18.942145470 -0700
+++ bar 2020-09-10 14:37:28.742465694 -0700
@@ -1,5 +1,10 @@
 /lib64/libboost_system.so.1.69.0: Found separate debug info file:
/usr/lib/debug//usr/lib64//libboost_system.so.1.69.0-1.69.0-18.fc32.x86_64.debug

+/usr/lib/debug//usr/lib64//libboost_system.so.1.69.0-1.69.0-18.fc32.x86_64.debug:
Found separate debug info file:
/usr/lib/debug/usr/lib64/../../.dwz/boost-1.69.0-18.fc32.x86_64
+
+
+/usr/lib/debug/usr/lib64/../../.dwz/boost-1.69.0-18.fc32.x86_64:     file
format elf64-x86-64
+


/usr/lib/debug//usr/lib64//libboost_system.so.1.69.0-1.69.0-18.fc32.x86_64.debug:
    file format elf64-x86-64

It gets the DWZ file now but I still don't get the location lists that I'm
looking for.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]