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-i686, revision 517d261dfafb7e5317b841b01ab853a76deb8128
Date: Mon, 02 Dec 2019 07:15:00 -0000 [thread overview]
Message-ID: <E1ibfvH-0000qz-4P@gdb-buildbot.osci.io> (raw)
In-Reply-To: <517d261dfafb7e5317b841b01ab853a76deb8128-master-breakage@gdb-build>
Unfortunately it seems that there is a breakage on GDB.
Commit title: 'Fix latent bug in tui_copy_source_line'
Revision: 517d261dfafb7e5317b841b01ab853a76deb8128
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 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
GEN stamp-version
CXX windows-tdep.o
CXX x86-linux-nat.o
CXX x86-nat.o
CXX x86-tdep.o
CXX xcoffread.o
GEN xml-builtin.c
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
CXX gdb.o
CXX aarch32-tdep.o
CXX ada-exp.o
CXX ada-lang.o
CXX ada-tasks.o
CXX ada-typeprint.o
CXX ada-valprint.o
CXX ada-varobj.o
CXX addrmap.o
CXX agent.o
CXX alloc.o
CXX annotate.o
CXX arc-tdep.o
CXX arch-utils.o
CXX arch/aarch32.o
CXX arch/arm-get-next-pcs.o
CXX arch/arm-linux.o
CXX arch/arm.o
CXX arch/i386.o
CXX arch/ppc-linux-common.o
CXX arch/riscv.o
CXX arm-bsd-tdep.o
CXX arm-fbsd-tdep.o
CXX arm-linux-tdep.o
CXX arm-nbsd-tdep.o
CXX arm-obsd-tdep.o
CXX arm-pikeos-tdep.o
CXX arm-symbian-tdep.o
CXX arm-tdep.o
CXX arm-wince-tdep.o
CXX auto-load.o
CXX auxv.o
CXX avr-tdep.o
CXX ax-gdb.o
CXX ax-general.o
CXX bcache.o
CXX bfd-target.o
CXX bfin-linux-tdep.o
CXX bfin-tdep.o
CXX block.o
CXX blockframe.o
CXX break-catch-sig.o
CXX break-catch-syscall.o
CXX break-catch-throw.o
CXX breakpoint.o
CXX bsd-uthread.o
CXX btrace.o
CXX build-id.o
CXX buildsym-legacy.o
CXX buildsym.o
CXX c-exp.o
CXX cp-name-parser.o
CXX d-exp.o
CXX f-exp.o
CXX go-exp.o
CXX m2-exp.o
CXX p-exp.o
CXX rust-exp.o
CXX version.o
CXX xml-builtin.o
GEN init.c
CXX init.o
CXXLD gdb
/usr/bin/ld: unittests/tui-selftests.o: in function `selftests::tui::run_tests()':
/home/gdb-buildbot-2/fedora-x86-64-2/fedora-i686/build/gdb/../../binutils-gdb/gdb/unittests/tui-selftests.c:31: undefined reference to `tui_copy_source_line[abi:cxx11](char const**, int, int, int, int)'
/usr/bin/ld: /home/gdb-buildbot-2/fedora-x86-64-2/fedora-i686/build/gdb/../../binutils-gdb/gdb/unittests/tui-selftests.c:36: undefined reference to `tui_copy_source_line[abi:cxx11](char const**, int, int, int, int)'
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:1911: gdb] Error 1
make[2]: Leaving directory '/home/gdb-buildbot-2/fedora-x86-64-2/fedora-i686/build/gdb'
make[1]: *** [Makefile:9230: all-gdb] Error 2
make[1]: Leaving directory '/home/gdb-buildbot-2/fedora-x86-64-2/fedora-i686/build'
make: *** [Makefile:852: all] Error 2
program finished with exit code 2
elapsedTime=417.350608
next prev parent reply other threads:[~2019-12-02 7:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-02 7:15 Oh dear. I regret to inform you that commit 517d261dfafb7e5317b841b01ab853a76deb8128 might be unfortunate gdb-buildbot
2019-12-02 7:15 ` gdb-buildbot [this message]
2019-12-02 8:19 ` Breakage on builder Fedora-x86_64-w64-mingw32, revision 517d261dfafb7e5317b841b01ab853a76deb8128 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=E1ibfvH-0000qz-4P@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).