Comment 20 for bug 1890435

I tried to isolate what was running concurrently and found 7 gcc calls.
I have set them up to run concurrently in endless loops each.
That way they reached a lot of iterations without triggering the issue :-/

I don't know how to continue :-/
But I can share a login to this system and show how to trigger the bug.

The following will get you there and trigger the bug usually in 1-2 loops (~4h on average)
$ ssh ubuntu@10.48.130.69
$ lxc exec groovy-gccfail bash
# cd qemu-5.0/
# i=1; export DEB_BUILD_OPTIONS=parallel=4; while debuild -i -us -uc -b -d; do echo "try $((i++)) complete" >> ~/build.log; done

@Doko could you take over from here as I'd hope you know how to force gcc to give you a dump?
I imported your key to the system mentioned above.