Hi Kane,

On Mon, 2026-07-13 at 15:41 +0000, [email protected] wrote:
> A new failure has been detected on builder elfutils-fedora-s390x while 
> building elfutils.
> 
> Full details are available at:
>     https://builder.sourceware.org/buildbot/#/builders/43/builds/565
> 
> Build state: failed test (failure)
> Revision: 22437a8e96db127ce6886e06a9c613cf19bab469
> Worker: fedora-s390x
> Build Reason: (unknown)
> Blamelist: Kane Wang <[email protected]>
> 
> [...]
> A new failure has been detected on builder elfutils-debian-ppc64 while 
> building elfutils.
> 
> Full details are available at:
>     https://builder.sourceware.org/buildbot/#/builders/63/builds/723
> 
> Build state: failed test (failure)
> Revision: 22437a8e96db127ce6886e06a9c613cf19bab469
> Worker: debian-ppc64
> Build Reason: (unknown)
> Blamelist: Kane Wang <[email protected]>
> 

These are both big endian machines, and they fail the same way on the
new testcase:

--- readelf.out 2026-07-13 13:39:25.906716471 +0000
+++ -   2026-07-13 13:39:25.911392375 +0000
@@ -1 +1,5 @@
-/var/lib/buildbot/workers/wildebeest/elfutils-debian-
ppc64/build/src/readelf: failed reading 'core-ioperm-huge.core':
invalid data
+
+Note segment of 16777236 bytes at offset 0x78:
+  Owner          Data size  Type
+  CORE            16777216  386_IOPERM
+    ioperm: <>
FAIL run-readelf-core-ioperm-huge.sh (exit status: 1)

I don't know yet if that is an existing bug reading core files with eu-
readelf or a specific bug for this note type.

Cheers,

Mark

Reply via email to