Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Wilson <jimw@sifive.com>
To: gdb-buildbot@sergiodj.net, gdb-patches@sourceware.org
Subject: Re: Breakage on builder Ubuntu-Aarch64-native-extended-gdbserver-m64, revision 2dc8dd17cd595bd7a1b0824c83380af52e633fc1
Date: Sat, 19 Jan 2019 19:02:00 -0000	[thread overview]
Message-ID: <27113bd3-3fc9-42d2-116a-91dbbb3f8e65@sifive.com> (raw)
In-Reply-To: <E1gktYs-0005C2-IL@kwanyin.sergiodj.net>

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.

Jim


  reply	other threads:[~2019-01-19 19:02 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 [this message]
2019-01-19 20:13     ` Sergio Durigan Junior
2019-01-21 10:27       ` Alan Hayward
2019-01-22 20:42         ` Sergio Durigan Junior

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=27113bd3-3fc9-42d2-116a-91dbbb3f8e65@sifive.com \
    --to=jimw@sifive.com \
    --cc=gdb-buildbot@sergiodj.net \
    --cc=gdb-patches@sourceware.org \
    /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