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 Ubuntu-Aarch64-m64, revision 01027315f54048dbaf03ac37455c2528c72a6d9b
Date: Wed, 15 Jan 2020 01:00:00 -0000	[thread overview]
Message-ID: <E1irWzx-0005Bo-Qd@gdb-buildbot.osci.io> (raw)
In-Reply-To: <01027315f54048dbaf03ac37455c2528c72a6d9b-master-breakage@gdb-build>

Unfortunately it seems that there is a breakage on GDB.

Commit title: 'Move gdbsupport to the top level'
Revision: 01027315f54048dbaf03ac37455c2528c72a6d9b

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    macroscope.o
  CXX    macrotab.o
  CXX    main.o
  CXX    maint-test-options.o
  CXX    maint-test-settings.o
  CXX    maint.o
  CXX    mdebugread.o
  CXX    mem-break.o
  CXX    memattr.o
  CXX    memory-map.o
  CXX    memrange.o
  CXX    mep-tdep.o
  CXX    mi/mi-cmd-break.o
  CXX    mi/mi-cmd-catch.o
  CXX    mi/mi-cmd-disas.o
  CXX    mi/mi-cmd-env.o
  CXX    mi/mi-cmd-file.o
  CXX    mi/mi-cmd-info.o
  CXX    mi/mi-cmd-stack.o
  CXX    mi/mi-cmd-target.o
  CXX    mi/mi-cmd-var.o
  CXX    mi/mi-cmds.o
  CXX    mi/mi-common.o
  CXX    mi/mi-console.o
  CXX    mi/mi-getopt.o
  CXX    mi/mi-interp.o
  CXX    mi/mi-main.o
  CXX    mi/mi-out.o
  CXX    mi/mi-parse.o
  CXX    mi/mi-symbol-cmds.o
  CXX    microblaze-linux-tdep.o
  CXX    microblaze-tdep.o
  CXX    minidebug.o
  CXX    minsyms.o
  CXX    mips-fbsd-tdep.o
  CXX    mips-linux-tdep.o
  CXX    mips-nbsd-tdep.o
  CXX    mips-sde-tdep.o
  CXX    mips-tdep.o
  CXX    mips64-obsd-tdep.o
  CXX    mipsread.o
  CXX    mn10300-linux-tdep.o
  CXX    mn10300-tdep.o
  CXX    moxie-tdep.o
  CXX    msp430-tdep.o
  CXX    namespace.o
  CXX    nat/aarch64-linux-hw-point.o
  CXX    nat/aarch64-linux.o
  CXX    nat/aarch64-sve-linux-ptrace.o
  CXX    nat/fork-inferior.o
In file included from ../../binutils-gdb/gdb/gdb_proc_service.h:22:0,
                 from ../../binutils-gdb/gdb/nat/aarch64-linux.h:25,
                 from ../../binutils-gdb/gdb/nat/aarch64-linux.c:23:
../../binutils-gdb/gdb/../gdbsupport/gdb_proc_service.h:87:22: error: conflicting declaration 'typedef unsigned int lwpid_t'
 typedef unsigned int lwpid_t;
                      ^~~~~~~
In file included from /usr/include/aarch64-linux-gnu/sys/ucontext.h:36:0,
                 from /usr/include/signal.h:306,
                 from ../gnulib/import/signal.h:52,
                 from ../../binutils-gdb/gdb/nat/aarch64-linux.h:22,
                 from ../../binutils-gdb/gdb/nat/aarch64-linux.c:23:
/usr/include/aarch64-linux-gnu/sys/procfs.h:115:17: note: previous declaration as 'typedef __pid_t lwpid_t'
 typedef __pid_t lwpid_t;
                 ^~~~~~~
In file included from ../../binutils-gdb/gdb/nat/aarch64-linux.c:26:0:
../../binutils-gdb/gdb/nat/gdb_ptrace.h:129:8: error: 'PTRACE_TYPE_RET' does not name a type
 extern PTRACE_TYPE_RET ptrace();
        ^~~~~~~~~~~~~~~
../../binutils-gdb/gdb/nat/aarch64-linux.c: In function 'ps_err_e aarch64_ps_get_thread_area(ps_prochandle*, lwpid_t, int, void**, int)':
../../binutils-gdb/gdb/nat/gdb_ptrace.h:150:19: error: 'PTRACE_TYPE_ARG1' was not declared in this scope
          ptrace ((PTRACE_TYPE_ARG1) request, pid, addr, data)
                   ^
../../binutils-gdb/gdb/nat/aarch64-linux.c:240:7: note: in expansion of macro 'ptrace'
   if (ptrace (PTRACE_GETREGSET, lwpid, NT_ARM_TLS, &iovec) != 0)
       ^~~~~~
../../binutils-gdb/gdb/nat/gdb_ptrace.h:150:10: error: 'ptrace' was not declared in this scope
          ptrace ((PTRACE_TYPE_ARG1) request, pid, addr, data)
          ^
../../binutils-gdb/gdb/nat/aarch64-linux.c:240:7: note: in expansion of macro 'ptrace'
   if (ptrace (PTRACE_GETREGSET, lwpid, NT_ARM_TLS, &iovec) != 0)
       ^~~~~~
../../binutils-gdb/gdb/nat/gdb_ptrace.h:150:10: note: suggested alternative: 'pwrite'
          ptrace ((PTRACE_TYPE_ARG1) request, pid, addr, data)
          ^
../../binutils-gdb/gdb/nat/aarch64-linux.c:240:7: note: in expansion of macro 'ptrace'
   if (ptrace (PTRACE_GETREGSET, lwpid, NT_ARM_TLS, &iovec) != 0)
       ^~~~~~
  CXX    nat/linux-namespaces.o
Makefile:1593: recipe for target 'nat/aarch64-linux.o' failed
make[2]: *** [nat/aarch64-linux.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory '/work/ubuntu-aarch64-m64/build/gdb'
Makefile:9647: recipe for target 'all-gdb' failed
make[1]: *** [all-gdb] Error 2
make[1]: Leaving directory '/work/ubuntu-aarch64-m64/build'
Makefile:852: recipe for target 'all' failed
make: *** [all] Error 2
program finished with exit code 2
elapsedTime=164.450742


  reply	other threads:[~2020-01-15  0:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-15  0:57 Oh dear. I regret to inform you that commit 01027315f54048dbaf03ac37455c2528c72a6d9b might be unfortunate gdb-buildbot
2020-01-15  1:00 ` gdb-buildbot [this message]
2020-01-15  1:03 ` Breakage on builder Ubuntu-Aarch64-native-extended-gdbserver-m64, revision 01027315f54048dbaf03ac37455c2528c72a6d9b gdb-buildbot
2020-01-15  2:34 ` Breakage on builder Ubuntu-Aarch64-native-gdbserver-m64, " gdb-buildbot
2020-01-17  0:02 ` Breakage on builder Fedora-i686, " gdb-buildbot
2020-01-17  0:03 ` Breakage on builder Fedora-x86_64-cc-with-index, " gdb-buildbot
2020-01-17  0:04 ` Breakage on builder Fedora-x86_64-m32, " gdb-buildbot
2020-01-17  0:06 ` Breakage on builder Fedora-x86_64-m64, " gdb-buildbot
2020-01-17  0:10 ` Breakage on builder Fedora-x86_64-native-extended-gdbserver-m32, " gdb-buildbot
2020-01-17  0:15 ` Breakage on builder Fedora-x86_64-native-gdbserver-m64, " gdb-buildbot
2020-01-17  0:15 ` Breakage on builder Fedora-x86_64-native-gdbserver-m32, " gdb-buildbot
2020-01-17  1:04 ` Breakage on builder Fedora-x86_64-native-extended-gdbserver-m64, " 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=E1irWzx-0005Bo-Qd@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