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/gdb-7.11-branch] Make gdb/linux-nat.c consider a waitstatus pending on the infrun side
Date: Wed, 25 May 2016 17:52:00 -0000 [thread overview]
Message-ID: <a0de87e7be6a58dfeb9bfb00172dbd975dabb72e@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT a0de87e7be6a58dfeb9bfb00172dbd975dabb72e ***
Author: Pedro Alves <palves@redhat.com>
Branch: gdb-7.11-branch
Commit: a0de87e7be6a58dfeb9bfb00172dbd975dabb72e
Make gdb/linux-nat.c consider a waitstatus pending on the infrun side
Working on the fix for gdb/19828, I saw
gdb.threads/attach-many-short-lived-threads.exp fail once in an
unusual way. Unfortunately I didn't keep debug logs, but it's an
issue similar to what's been fixed in remote.c a while ago --
linux-nat.c was not fetching the pending status from the right place.
gdb/ChangeLog:
2016-05-25 Pedro Alves <palves@redhat.com>
PR gdb/19828
* linux-nat.c (get_pending_status): If the thread reported the
event to the core and it's pending, use the pending status signal
number.
next reply other threads:[~2016-05-25 17:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-25 17:52 sergiodj+buildbot [this message]
2016-05-25 18:10 ` Failures on RHEL-s390x-m64, branch gdb-7.11-branch sergiodj+buildbot
2016-05-25 18:19 ` Failures on AIX-POWER7-plain, " sergiodj+buildbot
2016-05-25 18:25 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2016-05-25 18:32 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2016-05-25 18:38 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-05-25 18:42 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2016-05-25 18:45 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2016-05-25 18:48 ` Failures on Fedora-i686, " sergiodj+buildbot
2016-05-25 18:55 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2016-05-25 19:01 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2016-05-25 19:53 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2016-05-25 19:55 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot
2016-05-25 20:19 ` Failures on Debian-i686, " sergiodj+buildbot
2016-05-25 22:36 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2016-05-25 22:47 ` Failures on Debian-s390x-m64, " sergiodj+buildbot
2016-05-25 23:30 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-05-26 14:47 ` Failures on Fedora-ppc64be-cc-with-index, " sergiodj+buildbot
2016-05-26 14:52 ` Failures on Fedora-ppc64be-m64, " sergiodj+buildbot
2016-05-26 15:35 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot
2016-05-26 15:48 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-05-26 21:23 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-05-26 22:20 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot
2016-05-26 22:52 ` Failures on Fedora-ppc64le-m64, " 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=a0de87e7be6a58dfeb9bfb00172dbd975dabb72e@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).