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] Remove usage of find_inferior in win32-i386-low.c Date: Mon, 20 Nov 2017 03:48:00 -0000 [thread overview] Message-ID: <0b360f1926cb15edc39c661dac2f1a433fb288c0@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 0b360f1926cb15edc39c661dac2f1a433fb288c0 *** Author: Simon Marchi <simon.marchi@ericsson.com> Branch: master Commit: 0b360f1926cb15edc39c661dac2f1a433fb288c0 Remove usage of find_inferior in win32-i386-low.c Straightforward replacement of find_inferior with the overload of for_each_thread that filters on pid. I am able to build-test this patch, but not run it. gdb/gdbserver/ChangeLog: * win32-i386-low.c (update_debug_registers_callback): Rename to ... (update_debug_registers): ... this, return void, remove pid_p arg. (x86_dr_low_set_addr, x86_dr_low_set_control): Use for_each_thread.
next reply other threads:[~2017-11-20 3:48 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-11-20 3:48 sergiodj+buildbot [this message] 2017-11-20 3:48 ` Failures on Fedora-x86_64-m64, branch master sergiodj+buildbot 2017-11-20 3:52 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot 2017-11-20 3:52 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2017-11-20 4:00 ` Failures on Ubuntu-AArch64-native-gdbserver-m64, " sergiodj+buildbot 2017-11-20 4:03 ` Failures on Fedora-i686, " sergiodj+buildbot 2017-11-20 4:07 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot 2017-11-20 4:14 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2017-11-20 4:18 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot 2017-11-20 4:31 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot 2017-11-20 4:36 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot 2017-11-20 4:42 ` Failures on Ubuntu-AArch32-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=0b360f1926cb15edc39c661dac2f1a433fb288c0@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).