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 find_inferior_in_random
Date: Sun, 03 Dec 2017 06:09:00 -0000 [thread overview]
Message-ID: <83e1b6c13a285b4e1e852e1647667f09bb26892b@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT 83e1b6c13a285b4e1e852e1647667f09bb26892b ***
Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: 83e1b6c13a285b4e1e852e1647667f09bb26892b
Remove find_inferior_in_random
Replace with find_thread_in_random.
gdb/gdbserver/ChangeLog:
* inferiors.c (find_inferior_in_random): Remove.
* inferiors.h (find_inferior_in_random): Remove.
* linux-low.c (status_pending_p_callback): Return bool, accept
parameter ptid directly.
(linux_wait_for_event_filtered): Use find_thread_in_random.
(linux_wait_1): Likewise.
next reply other threads:[~2017-12-03 6:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-03 6:09 sergiodj+buildbot [this message]
2017-12-03 6:05 ` Failures on Fedora-x86_64-native-gdbserver-m32, branch master sergiodj+buildbot
2017-12-03 6:11 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2017-12-03 6:14 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2017-12-03 6:25 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2017-12-03 6:31 ` Failures on Fedora-i686, " sergiodj+buildbot
2017-12-03 6:50 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2017-12-03 7:52 ` Failures on Ubuntu-AArch64-native-gdbserver-m64, " sergiodj+buildbot
2017-12-03 9:52 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2017-12-03 10:18 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot
2017-12-03 10:43 ` 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=83e1b6c13a285b4e1e852e1647667f09bb26892b@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: link
Be 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).