** Changed in: binutils
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958389
Title:
Jammy builds of xen segfault, but only on launchpad x86 builders
To m
** Changed in: binutils (Debian)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958389
Title:
Jammy builds of xen segfault, but only on launchpad x86 builder
This bug was fixed in the package binutils - 2.37.90.20220130-0ubuntu2
---
binutils (2.37.90.20220130-0ubuntu2) jammy; urgency=medium
* Also ignore regressions for the cross packages.
-- Matthias Klose Sun, 30 Jan 2022 16:59:06 +0100
** Changed in: binutils (Ubuntu Jammy)
** Changed in: binutils (Debian)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958389
Title:
Jammy builds of xen segfault, but only on launchpad x86 builders
To man
** Changed in: binutils
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958389
Title:
Jammy builds of xen segfault, but only on launchpad x86 builders
To mana
** Also affects: binutils (Ubuntu Jammy)
Importance: Critical
Status: New
** Also affects: xen (Ubuntu Jammy)
Importance: Undecided
Status: Invalid
** Tags removed: rls-jj-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
** Tags added: fr-2001
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958389
Title:
Jammy builds of xen segfault, but only on launchpad x86 builders
To manage notifications about this bug go to:
ht
** Changed in: binutils (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958389
Title:
Jammy builds of xen segfault, but only on launchpad x86 builders
To manag
Launchpad has imported 1 comments from the remote bug at
https://sourceware.org/bugzilla/show_bug.cgi?id=28826.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://h
** Bug watch added: Sourceware.org Bugzilla #28826
https://sourceware.org/bugzilla/show_bug.cgi?id=28826
** Also affects: binutils via
https://sourceware.org/bugzilla/show_bug.cgi?id=28826
Importance: Unknown
Status: Unknown
** Bug watch added: Debian Bug tracker #1004269
https
** Tags added: rls-jj-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958389
Title:
Jammy builds of xen segfault, but only on launchpad x86 builders
To manage notifications about this bug g
For xen itself we know now how to "work around it" which is retry until running
on one of the new builders. Leaving the bug open as it clearly seems to be a
real issue.
I also leave the PPA as-is so that you can grab sources from there for
recreating this binutils issue.
--
You received this b
Being a platform dependent (thereby rather severe, but easy to miss)
crash in binutils I feel it is time to bump priority of this to get it
onto the radar avoiding to ship it that way (potentially breaking more)
in our next LTS.
** Changed in: binutils (Ubuntu)
Importance: Undecided => Critical
This build ran 10:26 -> 10:33 and the crash happened "in between". As i
said in local sbuild those are not fatal but on LP they are. Therefore
attaching the build log ...
** Attachment added: "build log that did not exit fatally, but triggered the
crash we also see on LP (there fatally)"
http
The build log I attached above shall help to spot the versions needed
for debug symbols to read this crash correctly.
** Attachment added: "Crash file of x86_64-linux-gnu-ld.bfd as seen in local
sbuild"
https://bugs.launchpad.net/ubuntu/+source/xen/+bug/1958389/+attachment/775/+files/_usr
Thanks for the hint,
in case anyone needs to do the same - you can see the associated builder right
when the build starts - then abort it immediately, refresh and rebuild.
That way you get 1 build try <1min, I got
lgw01 018
lgw01 044
lgw01 023
lcy02 001
And the build on the latter I let finish w
Thanks Colin, even without debug symbols that still is probably enough
to confirm it is actually the same crash that I see on my laptop.
While I do not see why it is fatal for the build on LP but not on local
sbuild or dpkg-buildpkg in a local VM it means that most likely someone
looking into this
It probably isn't useful, but the backtrace without extra debug symbols
looks like this:
buildd@dogfood-lgw01-amd64-001:/build/xen-jT2uET/xen-4.16.0/xen/arch/x86$ gdb
--args x86_64-linux-gnu-ld -mi386pep --subsystem=10
--image-base=0x82d04000 --stack=0,0 --heap=0,0
--section-alignment=0
I've tested manually on a staging lcy02 builder and it works fine there,
so worst case you should be able to retry until it happens to land on
lcy02.
I've reproduced the problem on a staging lgw01 builder. I need ddebs to
get a useful backtrace, so I've filed
https://code.launchpad.net/~cjwatson/
Hi Colin,
so far I've seen it only on lgw01, but I didn't mass-submit it yet to try the
other builders.
Is there a better way than re-building/re-submitting to get onto the lcy02?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
Both the failures linked here were on lgw01. Have you seen this on
lcy02 as well, or only lgw01?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958389
Title:
Jammy builds of xen segfault, but only
FYI: I've seen some shortening of the reported crashes going on.
For example in journal it was "x86_64-linux-gn" and in the build log it was
after "x86_64-linux-gnu-ld". The local (non fatal) crash I got eventually was
in "x86_64-linux-gnu-ld.bfd".
This might or might not be the same crash on LP
22 matches
Mail list logo
