This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: Breakage on builder Ubuntu-Aarch64-native-extended-gdbserver-m64, revision 2dc8dd17cd595bd7a1b0824c83380af52e633fc1
- From: Alan Hayward <Alan dot Hayward at arm dot com>
- To: Sergio Durigan Junior <sergiodj at redhat dot com>
- Cc: Jim Wilson <jimw at sifive dot com>, GDB Patches <gdb-patches at sourceware dot org>, nd <nd at arm dot com>
- Date: Mon, 21 Jan 2019 10:27:37 +0000
- Subject: Re: Breakage on builder Ubuntu-Aarch64-native-extended-gdbserver-m64, revision 2dc8dd17cd595bd7a1b0824c83380af52e633fc1
- References: <2dc8dd17cd595bd7a1b0824c83380af52e633fc1-master-breakage@gdb-build> <E1gktYs-0005C2-IL@kwanyin.sergiodj.net> <27113bd3-3fc9-42d2-116a-91dbbb3f8e65@sifive.com> <874la44d8x.fsf@redhat.com>
> On 19 Jan 2019, at 20:13, Sergio Durigan Junior <sergiodj@redhat.com> wrote:
>
> On Saturday, January 19 2019, Jim Wilson wrote:
>
>> On 1/19/19 8:33 AM, gdb-buildbot@sergiodj.net wrote:
>>> gcc: internal compiler error: Segmentation fault (program cc1)
>>> Please submit a full bug report,
>>> with preprocessed source if appropriate.
>>> See <file:///usr/share/doc/gcc-5/README.Bugs> for instructions.
>>> Makefile:1598: recipe for target 'elf32-moxie.lo' failed
>>> make[4]: *** [elf32-moxie.lo] Error 1
>>
>> This is a gcc internal error on a file I didn't touch, though it might
>> have been affected by changes to common elf headers. Looks more like
>> an unstable build system or a latent build system compiler bug, than a
>> problem with the patch I checked in.
>
> Hi Jim,
>
> This is a problem with the build machine. I've decided to temporarily
> disable its email notifications until we can figure things out.
>
> Thanks,
>
> --
> Sergio
> GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
> Please send encrypted e-mail if possible
> http://sergiodj.net/
Sergio,
Quick update on this. Looks like it is a memory issue.
From dmesg:
[190707.240268] Synchronous External Abort: synchronous parity or ECC error (0x96000018) at 0x0000ffff9e917000
We’re in the process of trying to get this sorted.
Alan.