public inbox for gdb-testers@sourceware.org help / color / mirror / Atom feed
From: sergiodj+buildbot@sergiodj.net To: gdb-testers@sourceware.org Subject: [binutils-gdb] Fix Solaris build Date: Thu, 12 Apr 2018 17:40:00 -0000 [thread overview] Message-ID: <70b33f195b0d76e140921db40c0bea5a7c9abc42@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 70b33f195b0d76e140921db40c0bea5a7c9abc42 *** Author: Pedro Alves <palves@redhat.com> Branch: master Commit: 70b33f195b0d76e140921db40c0bea5a7c9abc42 Fix Solaris build This commit fixes a bit of rot in procfs.c caused by recent changes. Specifically, the target_ops::to_detach change to pass down 'inferior *' missed updating a forward declation, and the change to use scoped_fd in more places missed removing one do_cleanups call. src/gdb/procfs.c: In function target_ops* procfs_target(): src/gdb/procfs.c:167:16: error: invalid conversion from void (*)(target_ops*, const char*, int) to void (*)(target_ops*, inferior*, int) [-fpermissive] t->to_detach = procfs_detach; ^ src/gdb/procfs.c: In function ssd* proc_get_LDT_entry(procinfo*, int): src/gdb/procfs.c:1624:17: error: old_chain was not declared in this scope do_cleanups (old_chain); ^ src/gdb/procfs.c: At global scope: src/gdb/procfs.c:90:13: error: void procfs_detach(target_ops*, const char*, int) declared static but never defined [-Werror=unused-function] static void procfs_detach (struct target_ops *, const char *, int); ^ src/gdb/procfs.c:1923:1: error: void procfs_detach(target_ops*, inferior*, int) defined but not used [-Werror=unused-function] procfs_detach (struct target_ops *ops, inferior *inf, int from_tty) ^ gdb/ChangeLog: 2018-04-12 Pedro Alves <palves@redhat.com> * procfs.c (procfs_detach): Make forward declaration's prototype match definition's protototype. (proc_get_LDT_entry): Remove stale do_cleanups call.
next reply other threads:[~2018-04-12 17:40 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-04-12 17:40 sergiodj+buildbot [this message] 2018-04-12 17:40 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot 2018-04-12 17:41 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot 2018-04-12 17:49 ` Failures on RHEL-s390x-m64, " sergiodj+buildbot 2018-04-12 18:21 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot 2018-04-12 19:13 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-w64-mingw32, branch master *** BREAKAGE *** sergiodj+buildbot 2018-04-12 19:26 ` Failures on Fedora-i686, branch master sergiodj+buildbot 2018-04-12 19:34 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2018-04-12 19:44 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2018-04-12 20:16 ` Failures on Debian-s390x-m64, " sergiodj+buildbot 2018-04-12 21:04 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot 2018-04-12 21:14 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot 2018-04-12 21:19 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot 2018-04-12 22:40 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot 2018-04-12 23:24 ` Failures on Ubuntu-AArch32-m32, " sergiodj+buildbot 2018-11-26 14:27 [binutils-gdb] Fix Solaris build sergiodj+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=70b33f195b0d76e140921db40c0bea5a7c9abc42@gdb-build \ --to=sergiodj+buildbot@sergiodj.net \ --cc=gdb-testers@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: linkBe 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).