Hi Nick, On Fri, Jan 17, 2025 at 10:31:49AM +0000, Nick Clifton wrote: > >But I also think this is a bug in binutils readelf (CCing nickc). > > > >It really should not even try to print the "interpreter" of a separate > >debuginfo file. > > Well yes and no. One of the main uses of readelf is to inspect potentially > broken or corrupt ELF files, so displaying the contents of the interpreter > field even when it is not expected to be meaningful could still be of use > to someone. > > What I have done however is to update readelf's sources so that it sanitizes > the interpreter string before displaying it. Where "sanitizes" == "converts > any non displaying characters into hex values". Nice solution! Nicer than what elfutils eu-readelf does, so I might steal it :) The real problem is what you say above. There is no way to distinguish between a real separate debuginfo file (where the interpreter doesn't make sense) and a (slightly) corrupted ELF file. Thanks, Mark -- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
