Page MenuHomeFreeBSD

readelf: use table-based DT_FLAGS and DT_FLAGS_1 decoding
ClosedPublic

Authored by emaste on Feb 1 2019, 3:09 PM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Dec 20, 8:50 PM
Unknown Object (File)
Thu, Dec 19, 3:22 PM
Unknown Object (File)
Sat, Dec 7, 9:09 AM
Unknown Object (File)
Wed, Nov 27, 3:51 AM
Unknown Object (File)
Oct 8 2024, 3:54 AM
Unknown Object (File)
Oct 8 2024, 3:54 AM
Unknown Object (File)
Oct 8 2024, 3:53 AM
Unknown Object (File)
Oct 8 2024, 3:30 AM
Subscribers

Details

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

brooks added a subscriber: brooks.

LGTM

contrib/elftoolchain/readelf/readelf.c
2741 ↗(On Diff #53509)

Would this make more sense to the user as something like:

printf(" unknown(0x%jx)", (uintmax_t)val);
This revision is now accepted and ready to land.Feb 1 2019, 6:18 PM
kib added inline comments.
contrib/elftoolchain/readelf/readelf.c
2736 ↗(On Diff #53509)

This is weird, why not do &= ~ ?

2741 ↗(On Diff #53509)

It would make more sense to print each unknown flag individually. At least I do find it more useful, from my experience with the Intel CPUID bits and DMAR capabilities reports.

This revision was automatically updated to reflect the committed changes.
contrib/elftoolchain/readelf/readelf.c
2741 ↗(On Diff #53509)

Not a bad idea, I will keep it in mind for a followup