...
qapi/qapi-visit-block-core.c: In function ‘visit_type_q_obj_BlockdevOptions_base_members’:
qapi/qapi-visit-block-core.c:6570:1: internal compiler error: Segmentation fault
6570 | }
| ^
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-10/README.Bugs> for instructions.
...
The bug is not reproducible, so it is likely a hardware or OS problem.
So the compiler itself is recognizing that it isn't the source code (alone) but some awkwardness that is flaky.
It seems qemu builds in groovy hit this in ~1/3 of the builds we do on armhf - not sure if that is enough for debugging for you?
There was another one in Groovy as of yesterday. /launchpad. net/~ci- train-ppa- service/ +archive/ ubuntu/ 4263/+packages /launchpadlibra rian.net/ 497497840/ buildlog_ ubuntu- groovy- armhf.qemu_ 1%3A5.0- 5ubuntu8~ ppa1_BUILDING. txt.gz
https:/
https:/
... visit-block- core.c: In function ‘visit_ type_q_ obj_BlockdevOpt ions_base_ members’ : visit-block- core.c: 6570:1: internal compiler error: Segmentation fault //usr/share/ doc/gcc- 10/README. Bugs> for instructions.
qapi/qapi-
qapi/qapi-
6570 | }
| ^
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:/
...
The bug is not reproducible, so it is likely a hardware or OS problem.
So the compiler itself is recognizing that it isn't the source code (alone) but some awkwardness that is flaky.
It seems qemu builds in groovy hit this in ~1/3 of the builds we do on armhf - not sure if that is enough for debugging for you?