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 de Vries <tdevries@suse.de>
Subject: Breakage on builder Fedora-x86_64-w64-mingw32, revision 4de026046bfc49013f9089aaf31bc3200adb5c77 [gdb-8.3-branch]
Date: Mon, 22 Jul 2019 00:38:00 -0000	[thread overview]
Message-ID: <E1hpMLD-0005pB-CG@gdb-buildbot.osci.io> (raw)
In-Reply-To: <4de026046bfc49013f9089aaf31bc3200adb5c77-gdb-8.3-branch-breakage@gdb-build>

Unfortunately it seems that there is a breakage on GDB.

Commit title: '[gdb/symtab] Fix symbol loading performance regression'
Revision: 4de026046bfc49013f9089aaf31bc3200adb5c77

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    ser-mingw.o
  CXX    sh-linux-tdep.o
  CXX    serial.o
  CXX    ser-tcp.o
  CXX    sh-nbsd-tdep.o
  CXX    sh-tdep.o
  CXX    skip.o
  CXX    sol2-tdep.o
  CXX    solib-aix.o
  CXX    solib-darwin.o
  CXX    solib-dsbt.o
  CXX    solib-frv.o
  CXX    solib-spu.o
  CXX    solib-svr4.o
  CXX    solib-target.o
  CXX    solib.o
  CXX    source-cache.o
  CXX    source.o
  CXX    sparc-linux-tdep.o
  CXX    sparc-nbsd-tdep.o
  CXX    sparc-obsd-tdep.o
  CXX    sparc-ravenscar-thread.o
  CXX    sparc-sol2-tdep.o
  CXX    sparc-tdep.o
  CXX    sparc64-fbsd-tdep.o
  CXX    sparc64-linux-tdep.o
  CXX    sparc64-nbsd-tdep.o
  CXX    sparc64-obsd-tdep.o
  CXX    sparc64-sol2-tdep.o
  CXX    sparc64-tdep.o
  CXX    spu-multiarch.o
  CXX    spu-tdep.o
  CXX    stabsread.o
  CXX    stack.o
  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    typeprint.o
  CXX    ui-file.o
  CXX    ui-out.o
  CXX    ui-style.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-nat.o
  CXX    windows-tdep.o
  CXX    x86-nat.o
  CXX    x86-tdep.o
  CXX    xcoffread.o
  CXX    xml-builtin.o
  CXX    xml-support.o
../../binutils-gdb/gdb/windows-nat.c: In member function 'virtual void windows_nat_target::create_inferior(const char*, const string&, char**, int)':
../../binutils-gdb/gdb/windows-nat.c:2849:26: warning: 'shell[0]' may be used uninitialized in this function [-Wmaybe-uninitialized]
   if (useshell && shell[0] != '\0')
                   ~~~~~~~^
  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    init.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=3485.738094


      reply	other threads:[~2019-07-22  0:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-22  0:38 Oh dear. I regret to inform you that commit 4de026046bfc49013f9089aaf31bc3200adb5c77 might be unfortunate [gdb-8.3-branch] gdb-buildbot
2019-07-22  0:38 ` 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=E1hpMLD-0005pB-CG@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