From: gdb-buildbot@sergiodj.net
To: gdb-patches@sourceware.org
To: gdb-patches@sourceware.org, Tom Tromey <tom@tromey.com>
Subject: Breakage on builder Fedora-x86_64-m32, revision cf82af058d2f1488d8f8a096d7e3b76d1d5a4f46
Date: Fri, 19 Jul 2019 11:15:00 -0000 [thread overview]
Message-ID: <E1hoQqu-0007ZK-Ft@gdb-buildbot.osci.io> (raw)
In-Reply-To: <cf82af058d2f1488d8f8a096d7e3b76d1d5a4f46-master-breakage@gdb-build>
Unfortunately it seems that there is a breakage on GDB.
Commit title: 'Remove TUI data window special case'
Revision: cf82af058d2f1488d8f8a096d7e3b76d1d5a4f46
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 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-windata.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/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 windows-tdep.o
CXX x86-linux-nat.o
CXX x86-nat.o
CXX x86-tdep.o
CXX xcoffread.o
CXX xml-support.o
CXX xml-syscall.o
CXX xml-tdesc.o
CXX xstormy16-tdep.o
CXX xtensa-config.o
CXX xtensa-linux-tdep.o
CXX xtensa-tdep.o
GEN init.c
CXX xml-builtin.o
CXX init.o
CXXLD gdb
command timed out: 1200 seconds without output running [b'make', b'-j4', b'all'], attempting to kill
process killed by signal 9
program finished with exit code -1
elapsedTime=2460.166811
next prev parent reply other threads:[~2019-07-19 11:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-19 11:15 Oh dear. I regret to inform you that commit cf82af058d2f1488d8f8a096d7e3b76d1d5a4f46 might be unfortunate gdb-buildbot
2019-07-19 11:15 ` gdb-buildbot [this message]
2019-07-19 12:33 ` Breakage on builder Fedora-x86_64-w64-mingw32, revision cf82af058d2f1488d8f8a096d7e3b76d1d5a4f46 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=E1hoQqu-0007ZK-Ft@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