From: Jan Beulich <jbeulich@suse.com>
To: Hans van Kranenburg <hans@knorrie.org>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: Debian Bug#1004269: Linker segfault while building src:xen
Date: Fri, 28 Jan 2022 08:04:44 +0100 [thread overview]
Message-ID: <8bf1f314-c1ba-eb8c-460b-d385a794b2b8@suse.com> (raw)
In-Reply-To: <9497ff64-8fe3-5d5d-303a-2d9f8709ade3@suse.com>
On 24.01.2022 09:40, Jan Beulich wrote:
> On 23.01.2022 22:52, Hans van Kranenburg wrote:
>> * 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.
For the sake of xen-devel, this looks to have been fixed in binutils:
https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=07c9f243b3a12cc6749bc02ee7b165859979348b
Jan
prev parent reply other threads:[~2022-01-28 7:05 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
2022-01-28 7:04 ` Jan Beulich [this message]
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=8bf1f314-c1ba-eb8c-460b-d385a794b2b8@suse.com \
--to=jbeulich@suse.com \
--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).