bug-binutils
[Top][All Lists]
Advanced

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

[Bug binutils/29075] objdump -S does not support debuginfod


From: nickc at redhat dot com
Subject: [Bug binutils/29075] objdump -S does not support debuginfod
Date: Mon, 09 May 2022 14:27:36 +0000

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

Nick Clifton <nickc at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |ASSIGNED
           Assignee|unassigned at sourceware dot org   |nickc at redhat dot com
   Last reconfirmed|                            |2022-05-09
     Ever confirmed|0                           |1

--- Comment #11 from Nick Clifton <nickc at redhat dot com> ---
(In reply to Martin Liska from comment #10)

> Thank you for the patch! But it does not work, when I debug it I can confirm
> show_line is called but there's early exit in:
> 
> if (! bfd_find_nearest_line_discriminator (abfd, section, syms, addr_offset
> 
> so your new code is not executed..

Ah - so there is no debug info in the binary being examined, and the BFD
library does not support debuginfod, so the find_nearest_line call fails...  

Presumably this will still be true if you add one of the display debug
information options to the command line, (eg -Wi) since the show_line() code
will still use the BFD library which has no connection to the dwarf
download/display code in the binutils/dwarf.c file, and so it will not find the
downloaded debug info held there.

So in order for -S to work, we either have to add debuginfod support to the BFD
library or else add a new find_nearest_line() type function to
binutils/dwarf.c.  I wonder which would be the best approach ?

-- 
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]