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 regcache_invalidate_pid Date: Sun, 03 Dec 2017 02:14:00 -0000 [thread overview] Message-ID: <634a3254c8fe1728c0202289afe594928094d860@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 634a3254c8fe1728c0202289afe594928094d860 *** Author: Simon Marchi <simon.marchi@polymtl.ca> Branch: master Commit: 634a3254c8fe1728c0202289afe594928094d860 Remove usage of find_inferior in regcache_invalidate_pid Replace with for_each_thread with pid filtering. regcache_invalidate_one is not longer needed, as it was only used to filter the pid. We can call regcache_invalidate_thread directly. gdb/gdbserver/ChangeLog: * regcache.c (regcache_invalidate_one): Remove. (regcache_invalidate_pid): use for_each_thread.
next reply other threads:[~2017-12-03 2:14 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-12-03 2:14 sergiodj+buildbot [this message] 2017-12-03 2:14 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot 2017-12-03 2:38 ` Failures on Fedora-i686, " sergiodj+buildbot 2017-12-03 2:44 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot 2017-12-03 2:54 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2017-12-03 3:13 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot 2017-12-03 3:15 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2017-12-03 3:21 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot 2017-12-03 3:49 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot 2017-12-03 4:14 ` 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=634a3254c8fe1728c0202289afe594928094d860@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).