Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: gdb-buildbot@sergiodj.net
To: gdb-patches@sourceware.org
To: gdb-patches@sourceware.org, Tom Tromey <tom@tromey.com>
Subject: Breakage on builder NetBSD-x86_64-m64, revision 098f9ed48e1c94a2624c825ba93d72b163d41196
Date: Thu, 18 Jul 2019 02:32:00 -0000	[thread overview]
Message-ID: <E1hnwDb-00073U-79@gdb-buildbot.osci.io> (raw)
In-Reply-To: <098f9ed48e1c94a2624c825ba93d72b163d41196-master-breakage@gdb-build>

Unfortunately it seems that there is a breakage on GDB.

Commit title: 'Always create an execution info window for a source window'
Revision: 098f9ed48e1c94a2624c825ba93d72b163d41196

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    opencl-lang.o
  CXX    osabi.o
  CXX    osdata.o
  YACC   p-exp.c
  CXX    p-exp.o
  CXX    p-lang.o
  CXX    p-typeprint.o
  CXX    p-valprint.o
  CXX    parse.o
  CXX    posix-hdep.o
  CXX    printcmd.o
  CXX    probe.o
  CXX    process-stratum-target.o
  CXX    producer.o
  CXX    progspace-and-thread.o
  CXX    progspace.o
  CXX    prologue-value.o
  CXX    psymtab.o
  CXX    python/python.o
  CXX    record-btrace.o
  CXX    record-full.o
  CXX    record.o
  CXX    regcache-dump.o
  CXX    regcache.o
  CXX    reggroups.o
  CXX    registry.o
  CXX    remote-fileio.o
  CXX    remote-notif.o
  CXX    remote.o
  CXX    reverse.o
  YACC   rust-exp.c
  CXX    rust-exp.o
  CXX    rust-lang.o
  CXX    selftest-arch.o
  CXX    sentinel-frame.o
  CXX    ser-base.o
  CXX    ser-event.o
  CXX    ser-pipe.o
  CXX    ser-tcp.o
  CXX    ser-uds.o
  CXX    ser-unix.o
  CXX    serial.o
  CXX    skip.o
  CXX    solib-svr4.o
  CXX    solib-target.o
  CXX    solib.o
  CXX    source-cache.o
  CXX    source.o
  CXX    stabsread.o
  CXX    stack.o
  CXX    stap-probe.o
  CXX    std-regs.o
  CXX    symfile-debug.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    tid-parse.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
../../binutils-gdb/gdb/tui/tui-layout.c: In function 'void show_data(tui_layout_type)':
../../binutils-gdb/gdb/tui/tui-layout.c:682:72: error: no matching function for call to 'tui_win_info::reset(int&, int, int, int)'
     tui_win_list[DATA_WIN]->reset (data_height, tui_term_width (), 0, 0);
                                                                        ^
In file included from ../../binutils-gdb/gdb/tui/tui-layout.c:31:0:
../../binutils-gdb/gdb/tui/tui-data.h:64:16: note: candidate: virtual void tui_gen_win_info::reset(tui_win_type, int, int, int, int)
   virtual void reset (enum tui_win_type win_type,
                ^
../../binutils-gdb/gdb/tui/tui-data.h:64:16: note:   candidate expects 5 arguments, 4 provided
Makefile:1630: recipe for target 'tui/tui-layout.o' failed
gmake[2]: *** [tui/tui-layout.o] Error 1
gmake[2]: Leaving directory '/data/motusgdb/gdbosci/netbsd-x86_64/build/gdb'
Makefile:9228: recipe for target 'all-gdb' failed
gmake[1]: *** [all-gdb] Error 2
gmake[1]: Leaving directory '/data/motusgdb/gdbosci/netbsd-x86_64/build'
Makefile:850: recipe for target 'all' failed
gmake: *** [all] Error 2
program finished with exit code 2
elapsedTime=686.546540


  parent reply	other threads:[~2019-07-18  2:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-18  1:05 Oh dear. I regret to inform you that commit 098f9ed48e1c94a2624c825ba93d72b163d41196 might be unfortunate gdb-buildbot
2019-07-18  1:05 ` Breakage on builder Solaris11-sparcv9-m64, revision 098f9ed48e1c94a2624c825ba93d72b163d41196 gdb-buildbot
2019-07-18 13:59   ` Tom Tromey
2019-07-18  1:36 ` Breakage on builder Solaris11-amd64-m64, " gdb-buildbot
2019-07-18  2:32 ` gdb-buildbot [this message]
2019-07-19 12:56 ` Breakage on builder Fedora-x86_64-cc-with-index, " gdb-buildbot
2019-07-19 12:58 ` Breakage on builder Fedora-x86_64-m32, " gdb-buildbot
2019-07-19 13:03 ` Breakage on builder Fedora-x86_64-m64, " gdb-buildbot
2019-07-19 13:06 ` Breakage on builder Fedora-x86_64-native-extended-gdbserver-m32, " gdb-buildbot
2019-07-19 13:10 ` Breakage on builder Fedora-x86_64-native-extended-gdbserver-m64, " gdb-buildbot
2019-07-19 13:13 ` Breakage on builder Fedora-x86_64-native-gdbserver-m64, " gdb-buildbot
2019-07-19 14:14 ` Breakage on builder Fedora-x86_64-native-gdbserver-m32, " 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=E1hnwDb-00073U-79@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