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 Fedora-x86_64-w64-mingw32, revision 3b3978bca2a204a772563c8e121e4a02be72e802
Date: Sat, 30 Nov 2019 02:52:00 -0000	[thread overview]
Message-ID: <E1iasrU-0001wG-A8@gdb-buildbot.osci.io> (raw)
In-Reply-To: <3b3978bca2a204a772563c8e121e4a02be72e802-master-breakage@gdb-build>

Unfortunately it seems that there is a breakage on GDB.

Commit title: 'Introduce thread-safe way to handle SIGSEGV'
Revision: 3b3978bca2a204a772563c8e121e4a02be72e802

You can find more details below:

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+


+++ The full log is too big to be posted here.
+++ These are the last 100 lines of it.

checking for lwpid_t in thread_db.h... no
checking for psaddr_t in thread_db.h... no
checking for dlopen in -ldl... no
checking whether the target supports __sync_*_compare_and_swap... yes
checking whether ADDR_NO_RANDOMIZE is declared... (cached) no
configure: updating cache .././config.cache
configure: creating ./config.status
config.status: creating Makefile
config.status: creating config.h
config.status: executing depdir commands
mkdir -p -- .deps
config.status: executing gdbdepdir commands
mkdir -p -- arch/.deps
mkdir -p -- gdbsupport/.deps
make[2]: Entering directory '/home/gdb-buildbot-2/fedora-x86-64-4/fedora-x86-64-mingw32/build/gdb'
/bin/sh ../../binutils-gdb/gdb/../mkinstalldirs arch/.deps
/bin/sh ../../binutils-gdb/gdb/../mkinstalldirs cli/.deps
mkdir -p -- arch/.deps
mkdir -p -- cli/.deps
/bin/sh ../../binutils-gdb/gdb/../mkinstalldirs mi/.deps
/bin/sh ../../binutils-gdb/gdb/../mkinstalldirs gdbsupport/.deps
mkdir -p -- mi/.deps
/bin/sh ../../binutils-gdb/gdb/../mkinstalldirs compile/.deps
mkdir -p -- compile/.deps
mkdir -p -- gdbsupport/.deps
/bin/sh ../../binutils-gdb/gdb/../mkinstalldirs tui/.deps
/bin/sh ../../binutils-gdb/gdb/../mkinstalldirs unittests/.deps
mkdir -p -- tui/.deps
/bin/sh ../../binutils-gdb/gdb/../mkinstalldirs guile/.deps
mkdir -p -- guile/.deps
mkdir -p -- unittests/.deps
/bin/sh ../../binutils-gdb/gdb/../mkinstalldirs python/.deps
/bin/sh ../../binutils-gdb/gdb/../mkinstalldirs target/.deps
mkdir -p -- target/.deps
mkdir -p -- python/.deps
/bin/sh ../../binutils-gdb/gdb/../mkinstalldirs nat/.deps
mkdir -p -- nat/.deps
  LEX    ada-lex.c
  YACC   ada-exp.c
  YACC   c-exp.c
/home/gdb-buildbot-2/fedora-x86-64-4/fedora-x86-64-mingw32/build/gdb/../../binutils-gdb/gdb/c-exp.y: warning: 42 shift/reduce conflicts [-Wconflicts-sr]
/home/gdb-buildbot-2/fedora-x86-64-4/fedora-x86-64-mingw32/build/gdb/../../binutils-gdb/gdb/c-exp.y: warning: 53 reduce/reduce conflicts [-Wconflicts-rr]
  CXX    c-lang.o
  CXX    c-typeprint.o
  CXX    c-valprint.o
  CXX    c-varobj.o
  CXX    charset.o
  CXX    cli-out.o
  CXX    cli/cli-cmds.o
  CXX    cli/cli-decode.o
  CXX    cli/cli-dump.o
  CXX    cli/cli-interp.o
  CXX    cli/cli-logging.o
  CXX    cli/cli-option.o
  CXX    cli/cli-script.o
  CXX    cli/cli-setshow.o
  CXX    cli/cli-style.o
  CXX    cli/cli-utils.o
  CXX    coff-pe-read.o
  CXX    coffread.o
  CXX    compile/compile-c-support.o
  CXX    compile/compile-c-symbols.o
  CXX    compile/compile-c-types.o
  CXX    compile/compile-cplus-symbols.o
  CXX    compile/compile-cplus-types.o
  CXX    compile/compile-loc2c.o
  CXX    compile/compile-object-load.o
  CXX    compile/compile-object-run.o
  CXX    compile/compile.o
  CXX    complaints.o
  CXX    completer.o
  CXX    continuations.o
  CXX    copying.o
  CXX    corefile.o
  CXX    corelow.o
  CXX    cp-abi.o
  YACC   cp-name-parser.c
/home/gdb-buildbot-2/fedora-x86-64-4/fedora-x86-64-mingw32/build/gdb/../../binutils-gdb/gdb/cp-name-parser.y:34.1-12: warning: POSIX Yacc does not support %pure-parser [-Wyacc]
   34 | %pure-parser
      | ^~~~~~~~~~~~
/home/gdb-buildbot-2/fedora-x86-64-4/fedora-x86-64-mingw32/build/gdb/../../binutils-gdb/gdb/cp-name-parser.y:34.1-12: warning: deprecated directive, use %define api.pure [-Wdeprecated]
   34 | %pure-parser
      | ^~~~~~~~~~~~
/home/gdb-buildbot-2/fedora-x86-64-4/fedora-x86-64-mingw32/build/gdb/../../binutils-gdb/gdb/cp-name-parser.y: warning: fix-its can be applied.  Rerun with option '--update'. [-Wother]
  CXX    cp-namespace.o
  CXX    cp-support.o
../../binutils-gdb/gdb/cp-support.c: In function 'void _initialize_cp_support()':
../../binutils-gdb/gdb/cp-support.c:2211:3: error: 'gdb_demangle_attempt_core_dump' was not declared in this scope
 2211 |   gdb_demangle_attempt_core_dump = can_dump_core (LIMIT_CUR);
      |   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  CXX    cp-valprint.o
make[2]: *** [Makefile:1651: cp-support.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory '/home/gdb-buildbot-2/fedora-x86-64-4/fedora-x86-64-mingw32/build/gdb'
make[1]: *** [Makefile:8917: all-gdb] Error 2
make[1]: Leaving directory '/home/gdb-buildbot-2/fedora-x86-64-4/fedora-x86-64-mingw32/build'
make: *** [Makefile:859: all] Error 2
program finished with exit code 2
elapsedTime=168.203467


      reply	other threads:[~2019-11-30  2:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-30  2:52 Oh dear. I regret to inform you that commit 3b3978bca2a204a772563c8e121e4a02be72e802 might be unfortunate gdb-buildbot
2019-11-30  2:52 ` 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=E1iasrU-0001wG-A8@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