Chris Lamb: > Hi Niels, > >> We are using readelf these days as it copes better with foreign >> architecture binaries. Although, as you have probably guessed by now, >> we have not to renamed our internal tooling to reflect the "objdump -> >> readelf" migration. > > No wonder I couldn't find the "objdump" invocation! > >> Does it also produce non-sense when you run "readelf -a -W" directly on >> the binaries? > > Yep! > > [...] > > > Regards, >
Ok, so we are now down to that either the binary is corrupt / has corrupted fields or readelf has a bug as root cause for the problem. * @Matthias; can you confirm whether the binary is as intended? Then there is a second problem in that lintian trusts itself (or the readelf output) too much. Ideally, it should not be possible to trigger this kind of warning even with a corrupt binary. Thanks, ~Niels
