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] Change iterate_over_lwps to take a gdb::function_view Date: Tue, 12 Mar 2019 17:07:00 -0000 [thread overview] Message-ID: <d3a70e03cf51c8fb6bc183eaff7559edffec2045@gdb-build> (raw) *** TEST RESULTS FOR COMMIT d3a70e03cf51c8fb6bc183eaff7559edffec2045 *** Author: Tom Tromey <tromey@adacore.com> Branch: master Commit: d3a70e03cf51c8fb6bc183eaff7559edffec2045 Change iterate_over_lwps to take a gdb::function_view This changes iterate_over_lwps to use a gdb::function_view. This was needed in order to make null_ptid and minus_one_ptid 'const'. gdb/ChangeLog 2019-03-12 Tom Tromey <tromey@adacore.com> * linux-nat.c (iterate_over_lwps): Update. (stop_callback): Remove parameter. (stop_wait_callback, detach_callback, resume_set_callback) (select_singlestep_lwp_callback, set_ignore_sigint) (status_callback, resumed_callback, resume_clear_callback) (kill_callback, kill_wait_callback, linux_nat_stop_lwp): Remove data parameter. (linux_nat_target::detach, linux_nat_target::resume) (linux_stop_and_wait_all_lwps, select_event_lwp) (linux_nat_filter_event, linux_nat_wait_1) (linux_nat_target::kill, linux_nat_target::stop) (linux_nat_target::stop): Update. (linux_nat_resume_callback): Change type. (resume_stopped_resumed_lwps, count_events_callback) (select_event_lwp_callback): Likewise. (linux_stop_lwp, linux_nat_stop_lwp): Update. * arm-linux-nat.c (struct update_registers_data): Remove. (update_registers_callback): Change type. (arm_linux_insert_hw_breakpoint1): Update. * nat/x86-linux-dregs.c (update_debug_registers_callback): Remove parameter. (x86_linux_dr_set_addr): Update. (x86_linux_dr_set_control): Update. * nat/linux-nat.h (iterate_over_lwps_ftype): Remove parameter. (iterate_over_lwps): Use gdb::function_view. * nat/aarch64-linux-hw-point.c (struct aarch64_dr_update_callback_param): Remove. (debug_reg_change_callback): Change type. (aarch64_notify_debug_reg_change): Update. * s390-linux-nat.c (s390_refresh_per_info): Update. gdb/gdbserver/ChangeLog 2019-03-12 Tom Tromey <tromey@adacore.com> * linux-low.c (iterate_over_lwps): Update.
next reply other threads:[~2019-03-12 17:07 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-03-12 17:07 sergiodj+buildbot [this message] 2019-03-12 17:07 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot 2019-03-12 17:58 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot 2019-03-12 18:29 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot 2019-03-13 16:05 ` Failures on Fedora-i686, " sergiodj+buildbot 2019-03-13 16:22 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot 2019-03-13 17:10 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2019-03-13 17:18 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2019-03-13 17:22 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2019-03-13 17:36 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot 2019-03-13 17:56 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot 2019-03-13 18:07 ` Failures on Fedora-x86_64-native-gdbserver-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=d3a70e03cf51c8fb6bc183eaff7559edffec2045@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).