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] target_set_syscall_catchpoint, use gdb::array_view and bool Date: Wed, 06 Dec 2017 23:13:00 -0000 [thread overview] Message-ID: <649a140ccf129ff79ea55ac0cc23ebddec0f02ef@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 649a140ccf129ff79ea55ac0cc23ebddec0f02ef *** Author: Pedro Alves <palves@redhat.com> Branch: master Commit: 649a140ccf129ff79ea55ac0cc23ebddec0f02ef target_set_syscall_catchpoint, use gdb::array_view and bool I noticed that we're passing down a data/size pair to target_ops::to_set_syscall_catchpoint. This commit makes use of gdb::array_view instead. While at it, use bool where appropriate as well. gdb/ChangeLog: * break-catch-syscall.c (insert_catch_syscall) (remove_catch_syscall): Adjust to pass reference to inf_data->syscalls_counts directly via gdb::array_view. * fbsd-nat.c (fbsd_set_syscall_catchpoint): Adjust to use bool and gdb::array_view. * linux-nat.c (linux_child_set_syscall_catchpoint): Likewise. * remote.c (remote_set_syscall_catchpoint): Likewise. * target-debug.h (target_debug_print_bool): New. (define target_debug_print_gdb_array_view_const_int): New. * target-delegates.c: Regenerate. * target.h (target_ops) <to_set_syscall_catchpoint>: Use gdb::array_view and bool. (target_set_syscall_catchpoint): Likewise.
next reply other threads:[~2017-12-06 23:13 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-12-06 23:13 sergiodj+buildbot [this message] 2017-12-06 23:13 ` Failures on Fedora-x86_64-m64, branch master sergiodj+buildbot 2017-12-06 23:13 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot 2017-12-06 23:15 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot 2017-12-06 23:31 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2017-12-06 23:33 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot 2017-12-06 23:34 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2017-12-06 23:41 ` Failures on Fedora-i686, " sergiodj+buildbot 2017-12-06 23:46 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2017-12-06 23:56 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot 2017-12-07 1:11 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot 2017-12-07 1:39 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot 2017-12-07 2:05 ` Failures on Ubuntu-AArch32-m32, " 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=649a140ccf129ff79ea55ac0cc23ebddec0f02ef@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).