From: gdb-buildbot@sergiodj.net
To: gdb-patches@sourceware.org
To: gdb-patches@sourceware.org, Andrew Burgess <andrew.burgess@embecosm.com>
Subject: Breakage on builder Fedora-x86_64-native-gdbserver-m32, revision 6b78c3f83c8bcbfa714aab7627ece9673b2d602a
Date: Wed, 17 Jul 2019 20:57:00 -0000 [thread overview]
Message-ID: <E1hnqzs-0002QE-1l@gdb-buildbot.osci.io> (raw)
In-Reply-To: <6b78c3f83c8bcbfa714aab7627ece9673b2d602a-master-breakage@gdb-build>
Unfortunately it seems that there is a breakage on GDB.
Commit title: 'gdb: Remove a non-const reference parameter'
Revision: 6b78c3f83c8bcbfa714aab7627ece9673b2d602a
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 gcore.o
CXX gdb-dlfcn.o
CXX gdb_bfd.o
CXX gdb_obstack.o
CXX gdb_regex.o
CXX gdb_usleep.o
CXX gdbarch-selftests.o
CXX gdbarch.o
CXX gdbsupport/agent.o
CXX gdbsupport/btrace-common.o
CXX gdbsupport/buffer.o
CXX gdbsupport/cleanups.o
CXX gdbsupport/common-debug.o
CXX gdbsupport/common-exceptions.o
CXX gdbsupport/common-regcache.o
CXX gdbsupport/common-utils.o
CXX gdbsupport/environ.o
CXX gdbsupport/errors.o
CXX gdbsupport/fileio.o
CXX gdbsupport/filestuff.o
CXX gdbsupport/format.o
CXX gdbsupport/gdb_tilde_expand.o
CXX gdbsupport/gdb_vecs.o
CXX gdbsupport/job-control.o
CXX gdbsupport/netstuff.o
CXX gdbsupport/new-op.o
CXX gdbsupport/pathstuff.o
CXX gdbsupport/posix-strerror.o
CXX gdbsupport/print-utils.o
CXX gdbsupport/ptid.o
CXX gdbsupport/rsp-low.o
CXX gdbsupport/run-time-clock.o
CXX gdbsupport/scoped_mmap.o
CXX gdbsupport/selftest.o
CXX gdbsupport/signals-state-save-restore.o
CXX gdbsupport/signals.o
CXX gdbsupport/tdesc.o
CXX gdbsupport/vec.o
CXX gdbsupport/xml-utils.o
CXX gdbtypes.o
CXX glibc-tdep.o
CXX gnu-v2-abi.o
CXX gnu-v3-abi.o
CXX go-exp.o
CXX go-lang.o
CXX go-typeprint.o
CXX go-valprint.o
CXX guile/guile.o
CXX guile/scm-arch.o
CXX guile/scm-auto-load.o
CXX guile/scm-block.o
CXX guile/scm-breakpoint.o
CXX guile/scm-cmd.o
CXX guile/scm-disasm.o
CXX guile/scm-exception.o
CXX guile/scm-frame.o
CXX guile/scm-gsmob.o
CXX guile/scm-iterator.o
CXX guile/scm-lazy-string.o
CXX guile/scm-math.o
CXX guile/scm-objfile.o
CXX guile/scm-param.o
CXX guile/scm-ports.o
CXX guile/scm-progspace.o
CXX guile/scm-pretty-print.o
CXX guile/scm-safe-call.o
CXX guile/scm-string.o
CXX guile/scm-symbol.o
CXX guile/scm-symtab.o
CXX guile/scm-type.o
CXX guile/scm-utils.o
CXX guile/scm-value.o
CXX h8300-tdep.o
CXX hppa-bsd-tdep.o
CXX hppa-linux-tdep.o
CXX hppa-obsd-tdep.o
CXX hppa-nbsd-tdep.o
CXX hppa-tdep.o
CXX i386-cygwin-tdep.o
CXX i386-bsd-tdep.o
CXX i386-darwin-tdep.o
CXX i386-dicos-tdep.o
CXX i386-fbsd-tdep.o
CXX i386-gnu-tdep.o
CXX i386-go32-tdep.o
CXX i386-linux-tdep.o
CXX i386-nbsd-tdep.o
CXX i386-nto-tdep.o
CXX i386-obsd-tdep.o
CXX i386-sol2-tdep.o
CXX i386-tdep.o
CXX i387-tdep.o
CXX ia64-linux-tdep.o
CXX ia64-tdep.o
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=4355.716806
prev parent reply other threads:[~2019-07-17 20:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-17 20:57 Oh dear. I regret to inform you that commit 6b78c3f83c8bcbfa714aab7627ece9673b2d602a might be unfortunate gdb-buildbot
2019-07-17 20:57 ` gdb-buildbot [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=E1hnqzs-0002QE-1l@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