From: gdb-buildbot@sergiodj.net
To: gdb-patches@sourceware.org
To: gdb-patches@sourceware.org, Simon Marchi <simon.marchi@polymtl.ca>
Subject: Breakage on builder Fedora-x86_64-m32, revision ad75efa628656716982f2674008952bfd2c268af
Date: Thu, 03 Oct 2019 23:13:00 -0000 [thread overview]
Message-ID: <E1iGAHw-0001Xe-Eq@gdb-buildbot.osci.io> (raw)
In-Reply-To: <ad75efa628656716982f2674008952bfd2c268af-master-breakage@gdb-build>
Unfortunately it seems that there is a breakage on GDB.
Commit title: 'gdb: include gdbarch.h in hppa-linux-nat.c'
Revision: ad75efa628656716982f2674008952bfd2c268af
You can find more details below:
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+++ The full log is too big to be posted here.
+++ These are the last 100 lines of it.
CXX stap-probe.o
CXX std-regs.o
CXX symfile-debug.o
CXX symfile-mem.o
CXX symfile.o
CXX symmisc.o
CXX symtab.o
CXX target-dcache.o
CXX target-descriptions.o
CXX target-float.o
CXX target-memory.o
CXX target.o
CXX target/waitstatus.o
CXX test-target.o
CXX thread-iter.o
CXX thread.o
CXX tic6x-linux-tdep.o
CXX tic6x-tdep.o
CXX tid-parse.o
CXX tilegx-linux-tdep.o
CXX tilegx-tdep.o
CXX top.o
CXX tracefile-tfile.o
CXX tracefile.o
CXX tracepoint.o
CXX trad-frame.o
CXX tramp-frame.o
CXX tui/tui-command.o
CXX tui/tui-data.o
CXX tui/tui-disasm.o
CXX tui/tui-file.o
CXX tui/tui-hooks.o
CXX tui/tui-interp.o
CXX tui/tui-io.o
CXX tui/tui-layout.o
CXX tui/tui-out.o
CXX tui/tui-regs.o
CXX tui/tui-source.o
CXX tui/tui-stack.o
CXX tui/tui-win.o
CXX tui/tui-wingeneral.o
CXX tui/tui-winsource.o
CXX tui/tui.o
CXX type-stack.o
CXX typeprint.o
CXX ui-file.o
CXX ui-out.o
CXX ui-style.o
CXX unittests/array-view-selftests.o
CXX unittests/child-path-selftests.o
CXX unittests/cli-utils-selftests.o
CXX unittests/common-utils-selftests.o
CXX unittests/copy_bitwise-selftests.o
CXX unittests/environ-selftests.o
CXX unittests/format_pieces-selftests.o
CXX unittests/function-view-selftests.o
CXX unittests/help-doc-selftests.o
CXX unittests/lookup_name_info-selftests.o
CXX unittests/memory-map-selftests.o
CXX unittests/memrange-selftests.o
CXX unittests/mkdir-recursive-selftests.o
CXX unittests/observable-selftests.o
CXX unittests/offset-type-selftests.o
CXX unittests/optional-selftests.o
CXX unittests/parse-connection-spec-selftests.o
CXX unittests/ptid-selftests.o
CXX unittests/rsp-low-selftests.o
CXX unittests/scoped_fd-selftests.o
CXX unittests/scoped_mmap-selftests.o
CXX unittests/scoped_restore-selftests.o
CXX unittests/string_view-selftests.o
CXX unittests/style-selftests.o
CXX unittests/tracepoint-selftests.o
CXX unittests/unpack-selftests.o
CXX unittests/utils-selftests.o
CXX unittests/xml-utils-selftests.o
CXX user-regs.o
CXX utils.o
CXX v850-tdep.o
CXX valarith.o
CXX valops.o
CXX valprint.o
CXX value.o
CXX varobj.o
CXX vax-nbsd-tdep.o
CXX vax-tdep.o
CXX version.o
CXX xml-builtin.o
CXX init.o
CXXLD gdb
collect2: fatal error: ld terminated with signal 9 [Killed]
compilation terminated.
make[2]: *** [Makefile:1883: gdb] Error 1
make[2]: Leaving directory '/home/gdb-buildbot/fedora-x86-64-3/fedora-x86-64-m32/build/gdb'
make[1]: *** [Makefile:9230: all-gdb] Error 2
make[1]: Leaving directory '/home/gdb-buildbot/fedora-x86-64-3/fedora-x86-64-m32/build'
make: *** [Makefile:852: all] Error 2
program finished with exit code 2
elapsedTime=1472.265200
next prev parent reply other threads:[~2019-10-03 23:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-03 23:13 Oh dear. I regret to inform you that commit ad75efa628656716982f2674008952bfd2c268af might be unfortunate gdb-buildbot
2019-10-03 23:13 ` gdb-buildbot [this message]
2019-10-03 23:21 ` Sergio Durigan Junior
2019-10-03 23:39 ` Breakage on builder Fedora-x86_64-m64, revision ad75efa628656716982f2674008952bfd2c268af gdb-buildbot
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=E1iGAHw-0001Xe-Eq@gdb-buildbot.osci.io \
--to=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