Reported in the PR -- nm might be more useful for this script.

I can also add --print-file-name to readelf though to make it always emit the File: line.

Mmmm,

$ readelf --print-file-name -r /usr/bin/mktemp
readelf: unrecognized option `--print-file-name'

In D15904#336884, @mat wrote:

Mmmm,

$ readelf --print-file-name -r /usr/bin/mktemp
readelf: unrecognized option `--print-file-name'

The option for readelf doesn't exist in HEAD yet, it's in review in D15908.

This looks fine to me. It's probably worth adding a comment explaining the use of ${NONEXISTENT} though.

In D15904#336954, @emaste wrote:

In D15904#336884, @mat wrote:

Mmmm,

$ readelf --print-file-name -r /usr/bin/mktemp
readelf: unrecognized option `--print-file-name'

The option for readelf doesn't exist in HEAD yet, it's in review in D15908.

Ah, that is why, and this was on 10.4, so a bit far from HEAD :-)

In D15904#336957, @emaste wrote:

This looks fine to me. It's probably worth adding a comment explaining the use of ${NONEXISTENT} though.

Yes, I have it in my local repository.

Another option: upon discussion with @dim we will likely end up installing llvm's llvm-objdump as objdump. It's broadly compatible, but the output format etc. might be slightly different.

Migrating to readelf is probably still the best option here though.

As the task is simple, the tool we actually end up using does not really matter.

What matters is that it is available on all supported releases :-)

In D15904#336964, @mat wrote:

What matters is that it is available on all supported releases :-)

Indeed, and readelf will always be available.