From: Jan Beulich <jbeulich@suse.com>
To: Hans van Kranenburg <hans@knorrie.org>
Cc: 1004269@bugs.debian.org, xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: Debian Bug#1004269: Linker segfault while building src:xen
Date: Mon, 24 Jan 2022 09:40:52 +0100 [thread overview]
Message-ID: <9497ff64-8fe3-5d5d-303a-2d9f8709ade3@suse.com> (raw)
In-Reply-To: <798c8459-7f28-c081-15bf-04ea94e8b711@knorrie.org>
On 23.01.2022 22:52, Hans van Kranenburg wrote:
> (To both the Debian bug # and xen-devel list, reply-all is fine)
> Hi Xen people,
>
> I just filed a bug at Debian on the binutils package, because since the
> latest binutils package update (Debian 2.37.50.20220106-2), Xen (both
> 4.14 and 4.16) fails to build with a segfault at the following point:
>
> 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)
>
> Full message and links to build logs etc are in the initial bug message,
> to be seen at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004269
>
> We (Debian Xen Team) are awaiting response, but I thought to also let
> you know already.
>
> * Does the above error 'ring a bell'?
> * Can you maybe also reproduce this in a development environment with
> very latest binutils?
I've tried with a 1.5 weeks old snapshot I had lying about; no
"success". But your and my builds are surely quite different anyway.
> * Maybe someone has a useful comment for the Debian binutils maintainer
> about what's happening in this step of the build?
It's xen.efi that's being linked; not sure what else to say.
> * Any suggestions about what we can do to help figure this out?
I'm pretty certain this needs debugging from the binutils side, so I
guess you will want to report it there (even more so with 2.38 around
the corner). I guess it's actually debugging ld or bisecting which
provide the best chance of figuring out what's going on.
Jan
> * We'll try to help debug, but will surely appreciate upstream help if
> things get too technical. It's simply the case that I did not have to
> look into a very similar issue before, so it's new.
>
> Thanks!
> Hans
>
next prev parent reply other threads:[~2022-01-24 8:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2a095341-a727-23d1-2dce-dd9caa72c920@knorrie.org>
2022-01-23 21:52 ` Debian Bug#1004269: Linker segfault while building src:xen Hans van Kranenburg
2022-01-24 8:40 ` Jan Beulich [this message]
2022-01-28 7:04 ` Jan Beulich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9497ff64-8fe3-5d5d-303a-2d9f8709ade3@suse.com \
--to=jbeulich@suse.com \
--cc=1004269@bugs.debian.org \
--cc=hans@knorrie.org \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).