From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Alan Hayward <Alan.Hayward@arm.com>
Cc: Jim Wilson <jimw@sifive.com>,
GDB Patches <gdb-patches@sourceware.org>, nd <nd@arm.com>
Subject: Re: Breakage on builder Ubuntu-Aarch64-native-extended-gdbserver-m64, revision 2dc8dd17cd595bd7a1b0824c83380af52e633fc1
Date: Tue, 22 Jan 2019 20:42:00 -0000 [thread overview]
Message-ID: <87imygwhk9.fsf@redhat.com> (raw)
In-Reply-To: <A67CDF93-C303-44A9-A389-ABC6C013CFEB@arm.com> (Alan Hayward's message of "Mon, 21 Jan 2019 10:27:37 +0000")
On Monday, January 21 2019, Alan Hayward wrote:
>> 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.
Thanks a lot for looking into this issue, Alan.
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
prev parent reply other threads:[~2019-01-22 20:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-19 16:33 Oh dear. I regret to inform you that commit 2dc8dd17cd595bd7a1b0824c83380af52e633fc1 might be unfortunate gdb-buildbot
2019-01-19 16:33 ` Breakage on builder Ubuntu-Aarch64-native-extended-gdbserver-m64, revision 2dc8dd17cd595bd7a1b0824c83380af52e633fc1 gdb-buildbot
2019-01-19 19:02 ` Jim Wilson
2019-01-19 20:13 ` Sergio Durigan Junior
2019-01-21 10:27 ` Alan Hayward
2019-01-22 20:42 ` Sergio Durigan Junior [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87imygwhk9.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=Alan.Hayward@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=jimw@sifive.com \
--cc=nd@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox