[Bug 1890435] Re: gcc-10 breaks on armhf (flaky): internal compiler error: Segmentation fault
Christian Ehrhardt
1890435 at bugs.launchpad.net
Wed Sep 23 14:34:49 UTC 2020
I got the crash in the repro env.
dmesg holds no OOM which is good - also no other dmesg/journal entry that would be related.
It might be depending on concurrent execution as this was the primary change to last time.
And not having set up apport/whoopsie to catch the crash :-/
I've installed them now and run the formerly breaking command in a loop.
For the sake of "just eating cpu cycles" I have spawned some cpu hogs in the background.
But with all that in place it ran the compile 300 times without a crash :-/
It seems I have to re-run in the build env and hope that apport will
catch it into /var/crash this time :-/
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to gcc-10 in Ubuntu.
https://bugs.launchpad.net/bugs/1890435
Title:
gcc-10 breaks on armhf (flaky): internal compiler error: Segmentation
fault
Status in gcc-10 package in Ubuntu:
New
Bug description:
Hi,
this could be the same as bug 1887557 but as I don't have enough data I'm filing it as individual issue for now.
I have only seen this happening on armhf so far.
In 2 of 5 groovy builds of qemu 5.0 this week I have hit the issue, but it is flaky.
Flakyness:
1. different file
first occurrence
/<<PKGBUILDDIR>>/target/s390x/excp_helper.c:544:1: internal compiler error: Segmentation fault
second occurrence
/<<PKGBUILDDIR>>/linux-user/syscall.c:12479:1: internal compiler error: Segmentation fault
Being so unreliable I can't provide mcuh more yet.
I filed it mostly for awareness and so that I can be dup'ed onto the right but if there is a better one.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-10/+bug/1890435/+subscriptions
More information about the foundations-bugs
mailing list