bug-binutils
[Top][All Lists]
Advanced

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

[Bug binutils/27309] readelf --debug-dump=info --wide output changes in


From: mliska at suse dot cz
Subject: [Bug binutils/27309] readelf --debug-dump=info --wide output changes in 2.36
Date: Tue, 02 Feb 2021 08:41:42 +0000

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

--- Comment #3 from Martin Liska <mliska at suse dot cz> ---
(In reply to Nick Clifton from comment #2)
> Hi Martin,
> 
>   The change was made so that the output from the binutils readelf would be
> closer to that of the elfutils readelf.  Vis:
> 
> Old Binutils:
>     <14>   DW_AT_name       : (indirect string, offset: 0x69):
> ../sysdeps/x86_64/crti.S
> 
> 2.36 Binutils:
>    <14>   DW_AT_name        : (strp) (offset: 0x69): ../sysdeps/x86_64/crti.S
>  
> Elfutils:
>           name                (strp) "../sysdeps/x86_64/crti.S"

I've got this point, makes sense. But I don't get why is that related to --wide
option?
To be honest, the output of non-wide mode is longer and more verbose than
--wide option
output:

$ readelf --debug-dump=info --wide /tmp/sample_struct.o | head -n20 | grep
offset
    <11>   DW_AT_name        : (strp) (offset: 0x12d):
mpers-m32/sample_struct.c
    <15>   DW_AT_comp_dir    : (strp) (offset: 0x89):
/home/abuild/rpmbuild/BUILD/strace-5.10
    <20>   DW_AT_name        : (strp) (offset: 0x56): unsigned char

$ readelf --debug-dump=info /tmp/sample_struct.o | head -n20 | grep offset
    <11>   DW_AT_name        : (indirect string, offset: 0x12d):
mpers-m32/sample_struct.c
    <15>   DW_AT_comp_dir    : (indirect string, offset: 0x89):
/home/abuild/rpmbuild/BUILD/strace-5.10
    <20>   DW_AT_name        : (indirect string, offset: 0x56): unsigned char

...

>   Can the strace configure script be adapted to cope with both versions 
>   of readelf's output ?

I can report that to them. It's unpleasant that parsing would depend
on the version of binutils.

Thanks,
Martin

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