Re: rpmlint+readelf corrupted interpreter on generated binaries

2025-01-17 Thread Mark Wielaard
Hi Nick, On Fri, Jan 17, 2025 at 10:31:49AM +, 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

Re: rpmlint+readelf corrupted interpreter on generated binaries

2025-01-17 Thread Nick Clifton
Hi Mark, 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

Re: rpmlint+readelf corrupted interpreter on generated binaries

2025-01-16 Thread Mark Wielaard
Hi! (Added nickc to the CC, see below) On Wed, Jan 15, 2025 at 01:52:24PM +0100, Miro Hrončok wrote: > On 15. 01. 25 10:18, Robin Jarry wrote: > >I found out that rpmlint errors out without producing any meaningful result > >when the analyzed RPMs contain binaries: > > > > sh-5.2# strace -f -e tr

Re: rpmlint+readelf corrupted interpreter on generated binaries

2025-01-16 Thread Carlos Rodriguez-Fernandez
Now I recall, it was happening in Zulu CI for my package, and all I could do was to ignore it as known issue while waiting for the rpmlint update. No workaround. On 1/15/25 8:33 AM, Carlos Rodriguez-Fernandez wrote: Thank you Miro, I was certain that I had sent a fix for that to rpmlint. The

Re: rpmlint+readelf corrupted interpreter on generated binaries

2025-01-15 Thread Carlos Rodriguez-Fernandez
Thank you Miro, I was certain that I had sent a fix for that to rpmlint. The problem went away in my package in the CI (bodhi or Zulu, can't recall), perhaps rpmlint was updated for the affected CI back then or was removed from the gating/ci pipelines, or I removed rpmlint from the gating/ci.

Re: rpmlint+readelf corrupted interpreter on generated binaries

2025-01-15 Thread Miro Hrončok
On 15. 01. 25 10:18, Robin Jarry wrote: Hi folks, I found out that rpmlint errors out without producing any meaningful result when the analyzed RPMs contain binaries: sh-5.2# strace -f -e trace=execve -s 65536 rpmlint build/RPMS/aerc-*.rpm ... [pid 107] execve("/usr/bin/readelf", ["readelf

Re: rpmlint+readelf corrupted interpreter on generated binaries

2025-01-15 Thread Zbigniew Jędrzejewski-Szmek
On Wed, Jan 15, 2025 at 10:18:28AM +0100, Robin Jarry wrote: > Hi folks, > > I found out that rpmlint errors out without producing any meaningful result > when the analyzed RPMs contain binaries: rpmlint should not blindly assume that output is valid text, but should probably print a meaningful