On 10/6/20 3:05 PM, Florian Weimer wrote:
* Steve Grubb:
> I was doing some binary analysis of files in F33 and have run across
> something odd.
>
> readelf -s /usr/sbin/auditd | grep GLIBC
>
> produces a lot of output like:
>
> 182: 0000000000000000 0 FUNC GLOBAL DEFAULT UND [...](a)GLIBC_2.2.5 (3)
> 184: 0000000000000000 0 FUNC GLOBAL DEFAULT UND [...](a)GLIBC_2.2.5 (3)
> 185: 0000000000000000 0 FUNC GLOBAL DEFAULT UND [...](a)GLIBC_2.2.5 (3)
> 186: 0000000000000000 0 FUNC GLOBAL DEFAULT UND [...](a)GLIBC_2.2.5 (3)
> 187: 0000000000000000 0 FUNC GLOBAL DEFAULT UND [...](a)GLIBC_2.3.2 (2)
> 191: 0000000000000000 0 FUNC GLOBAL DEFAULT UND alarm(a)GLIBC_2.2.5 (3)
> 194: 0000000000000000 0 FUNC GLOBAL DEFAULT UND [...](a)GLIBC_2.2.5 (3)
> 195: 0000000000000000 0 FUNC GLOBAL DEFAULT UND close(a)GLIBC_2.2.5 (3)
> 197: 0000000000000000 0 FUNC GLOBAL DEFAULT UND [...](a)GLIBC_2.2.5 (3)
>
> It's missing a lot of symbols. Is this something with readelf or an odd
> effect of the LTO changes?
This question looks familiar.
It's a deliberate change to indicate truncation. Use readelf -sW if you
want to avoid it. Truncation has been silent before, so it's necessary
to educate users about readelf -W.
I think I may have used --wide in my test because I wanted to see more
info...
jeff