Comment 18 for bug 1890435

Interim Summary:
- hits armhf compiles of various large source projects, chances are it it completely random
  and just hits those more likely by compiling more
- build system auto-retries the compiles and they work on retry eventually reported as "The bug
  is not reproducible, so it is likely a hardware or OS problem."
- The bug always occurs on different source files, retrying a failed one works for hundreds of
  times so it seems to be sort of random when it hits and not tied to the source.
- It seems we need concurrency to trigger it, but again it might just have increases the
  likeliness
- I can trigger it reliably now in ~2-8h of compile time on Canonistack when building qemu
  on an armhf LXD container on a arm64 Hosts (same as the builders)
- Despite my tries I'm unable to gather a crash dump of the gcc segfault and would be happy
  about a hint/advise on that.