Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Tom Tromey <tom@tromey.com>,  gdb-patches@sourceware.org
Cc: Alan Hayward <alan.hayward@arm.com>
Subject: Re: Breakage on builder Ubuntu-Aarch64-m64, revision cfeadda545c4961877969e6a66be79278696e012
Date: Wed, 09 Jan 2019 16:25:00 -0000	[thread overview]
Message-ID: <87r2dlol3v.fsf@redhat.com> (raw)
In-Reply-To: <E1gh6tT-0006jv-Ka@kwanyin.sergiodj.net> (gdb-buildbot's message	of "Wed, 09 Jan 2019 00:59:11 -0500")

On Wednesday, January 09 2019, gdb-buildbot wrote:

> Unfortunately it seems that there is a breakage on GDB.

Hi Alan,

Would it be possible to take a look at the aarch64 buildslave?  IIRC,
this is not the first time we've seen an ICE happening there.

Thanks a lot,

> Commit title: 'Fix build failure with macOS bison'
> Revision: cfeadda545c4961877969e6a66be79278696e012
>
> You can find more details below:
>
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
> Buildslave:
> 	ubuntu16-aarch64
>
> Full Build URL:
> 	<http://gdb-build.sergiodj.net/builders/Ubuntu-Aarch64-m64/builds/4844>
>
> Commit(s) tested:
> 	cfeadda545c4961877969e6a66be79278696e012
>
> Author(s) (in the same order as the commits):
> 	Tom Tromey <tom@tromey.com>
>
> Subject:
> 	Fix build failure with macOS bison
>
> Testsuite log (gdb.sum and gdb.log) URL(s):
> 	<http://gdb-build.sergiodj.net/results/Ubuntu-Aarch64-m64/cf/cfeadda545c4961877969e6a66be79278696e012/>
>
> *** Failed to compiled GDB.  ***
> ============================
>
> +++ The full log is too big to be posted here.
> +++ These are the last 100 lines of it.
>
>   CXX    cli/cli-cmds.o
>   CXX    cli/cli-decode.o
>   CXX    cli/cli-dump.o
>   CXX    cli/cli-interp.o
>   CXX    cli/cli-logging.o
>   CXX    cli/cli-script.o
>   CXX    cli/cli-setshow.o
>   CXX    cli/cli-style.o
>   CXX    cli/cli-utils.o
>   CXX    coff-pe-read.o
>   CXX    coffread.o
>   CXX    common/agent.o
>   CXX    common/btrace-common.o
>   CXX    common/buffer.o
>   CXX    common/cleanups.o
>   CXX    common/common-debug.o
>   CXX    common/common-exceptions.o
>   CXX    common/common-regcache.o
>   CXX    common/common-utils.o
>   CXX    common/environ.o
>   CXX    common/errors.o
>   CXX    common/fileio.o
>   CXX    common/filestuff.o
>   CXX    common/format.o
>   CXX    common/gdb_tilde_expand.o
>   CXX    common/gdb_vecs.o
>   CXX    common/job-control.o
>   CXX    common/netstuff.o
>   CXX    common/new-op.o
>   CXX    common/pathstuff.o
>   CXX    common/posix-strerror.o
>   CXX    common/print-utils.o
>   CXX    common/ptid.o
>   CXX    common/rsp-low.o
>   CXX    common/run-time-clock.o
>   CXX    common/scoped_mmap.o
>   CXX    common/selftest.o
>   CXX    common/signals-state-save-restore.o
>   CXX    common/signals.o
>   CXX    common/tdesc.o
>   CXX    common/vec.o
>   CXX    common/xml-utils.o
>   CXX    compile/compile-c-support.o
>   CXX    compile/compile-c-symbols.o
>   CXX    compile/compile-c-types.o
>   CXX    compile/compile-cplus-symbols.o
>   CXX    compile/compile-cplus-types.o
>   CXX    compile/compile-loc2c.o
>   CXX    compile/compile-object-load.o
>   CXX    compile/compile-object-run.o
>   CXX    compile/compile.o
>   CXX    complaints.o
>   CXX    completer.o
>   CXX    continuations.o
>   CXX    copying.o
>   CXX    corefile.o
>   CXX    corelow.o
>   CXX    cp-abi.o
>   CXX    cp-name-parser.o
>   CXX    cp-namespace.o
>   CXX    cp-support.o
>   CXX    cp-valprint.o
>   CXX    cris-linux-tdep.o
>   CXX    cris-tdep.o
>   CXX    csky-linux-tdep.o
>   CXX    csky-tdep.o
>   CXX    ctf.o
>   CXX    d-exp.o
>   CXX    d-lang.o
>   CXX    d-namespace.o
>   CXX    d-valprint.o
>   CXX    dbxread.o
>   CXX    dcache.o
>   CXX    debug.o
>   CXX    demangle.o
>   CXX    dicos-tdep.o
>   CXX    dictionary.o
>   CXX    disasm-selftests.o
>   CXX    disasm.o
>   CXX    dtrace-probe.o
>   CXX    dummy-frame.o
>   CXX    dwarf-index-cache.o
>   CXX    dwarf-index-common.o
>   CXX    dwarf-index-write.o
>   CXX    dwarf2-frame-tailcall.o
>   CXX    dwarf2-frame.o
> g++: internal compiler error: Segmentation fault (program cc1plus)
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <file:///usr/share/doc/gcc-5/README.Bugs> for instructions.
> Makefile:1641: recipe for target 'dwarf-index-write.o' failed
> make[2]: *** [dwarf-index-write.o] Error 4
> make[2]: *** Waiting for unfinished jobs....
> make[2]: Leaving directory '/home/gdb_buildbot/ubuntu16-aarch64/ubuntu-aarch64-m64/build/gdb'
> Makefile:8792: recipe for target 'all-gdb' failed
> make[1]: *** [all-gdb] Error 2
> make[1]: Leaving directory '/home/gdb_buildbot/ubuntu16-aarch64/ubuntu-aarch64-m64/build'
> Makefile:849: recipe for target 'all' failed
> make: *** [all] Error 2
> ============================

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/


  reply	other threads:[~2019-01-09 16:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-09  5:59 Oh dear. I regret to inform you that commit cfeadda545c4961877969e6a66be79278696e012 might be unfortunate gdb-buildbot
2019-01-09  5:59 ` Breakage on builder Ubuntu-Aarch64-m64, revision cfeadda545c4961877969e6a66be79278696e012 gdb-buildbot
2019-01-09 16:25   ` Sergio Durigan Junior [this message]
2019-01-10  9:54     ` Alan Hayward

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=87r2dlol3v.fsf@redhat.com \
    --to=sergiodj@redhat.com \
    --cc=alan.hayward@arm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.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