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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890435 Title: gcc-10 breaks on armhf (flaky): internal compiler error: Segmentation fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-10/+bug/1890435/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
