Package: src:binutils
Version: 2.37.50.20220106-2
X-Debbugs-CC: pkg-xen-de...@lists.alioth.debian.org
Hi,
With the last binutils version src:xen starts to FTBFS.
---- >8 ---- Xen 4.16 for experimental ---- >8 ----
* Last passed build, using binutils 2.37-10.
Job overview:
https://salsa.debian.org/xen-team/debian-xen/-/pipelines/329021
Full log:
https://salsa.debian.org/xen-team/debian-xen/-/jobs/2290845/raw
* First failed build, using the same source code, and using binutils
2.37.50.20220106-2:
Job overview:
https://salsa.debian.org/xen-team/debian-xen/-/pipelines/338409
Full log:
https://salsa.debian.org/xen-team/debian-xen/-/jobs/2375744/raw
At the end of the full log, the failure can be observed:
x86_64-linux-gnu-ld -mi386pep --subsystem=10
--image-base=0xffff82d040000000 --stack=0,0 --heap=0,0
--section-alignment=0x200000 --file-alignment=0x20
--major-image-version=4 --minor-image-version=16 --major-os-version=2
--minor-os-version=0 --major-subsystem-version=2
--minor-subsystem-version=0 --no-insert-timestamp --build-id=sha1 -T
efi.lds -N prelink.o
/builds/xen-team/debian-xen/debian/output/source_dir/xen/common/symbols-dummy.o
-b pe-x86-64 efi/buildid.o -o
/builds/xen-team/debian-xen/debian/output/source_dir/xen/.xen.efi.0xffff82d040000000.0
&& :
Segmentation fault (core dumped)
The above logs are for src:xen 4.16.0-1~exp1 which we were about to
upload to experimental.
---- >8 ---- Xen 4.14 currently in unstable ---- >8 ----
I also triggered a CI run again for the current src:xen
4.14.3+32-g9de3671772-1. The same segfault happens there, and both for
the amd64 and i386 build test (i386 is no longer included for Xen 4.16).
Job overview:
https://salsa.debian.org/xen-team/debian-xen/-/pipelines/340556
Full logs:
https://salsa.debian.org/xen-team/debian-xen/-/jobs/2394079/raw
https://salsa.debian.org/xen-team/debian-xen/-/jobs/2394080/raw
---- >8 ----
So, this is what we observe. In the Debian Xen team, there's not a great
amount of knowledge about the exact internals of what happens here.
* At least, we can let you know there's a regression.
* Currently progress on our Xen 4.16 upload is blocked, and we also
can't do updates of the current Xen 4.14 packages (e.g. because of
security fixes).
* We're available to help debugging this issue if needed. We'll need
guidance, so it will mean that we'll work based on your instructions.
* After sending this report and getting the confirmation from the BTS,
I'll send a reply with the upstream Xen development mailing list in Cc.
Thanks in advance,
Hans van Kranenburg
