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] Add test case for a known hang in infrun Date: Fri, 20 Apr 2018 03:25:00 -0000 [thread overview] Message-ID: <d27d16bfdc3f275b379793214db9bd9467b6f0f8@gdb-build> (raw) *** TEST RESULTS FOR COMMIT d27d16bfdc3f275b379793214db9bd9467b6f0f8 *** Author: Richard Bunt <richard.bunt@arm.com> Branch: master Commit: d27d16bfdc3f275b379793214db9bd9467b6f0f8 Add test case for a known hang in infrun The hang occurs when GDB tries to call inferior functions on two different threads with scheduler-locking turned on. The first call works fine, with the call to infrun_async(1) causing the signal_handler to be marked and the event to be handled, but then the event loop resets the "ready" member to zero, while leaving infrun_is_async set to 1. As a result, GDB hangs if the user switches to another thread and calls a second function because calling infrun_async(1) a second time has no effect, meaning the inferior call events are never handled. The added test case provokes the above issue. gdb/testsuite/ChangeLog: * gdb.threads/multiple-successive-infcall.c: New test. * gdb.threads/multiple-successive-infcall.exp: New file.
next reply other threads:[~2018-04-20 3:25 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-04-20 3:25 sergiodj+buildbot [this message] 2018-04-20 3:26 ` Failures on Fedora-x86_64-native-gdbserver-m32, branch master sergiodj+buildbot 2018-04-20 3:27 ` Failures on Fedora-i686, " sergiodj+buildbot 2018-04-20 3:41 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot 2018-04-20 3:43 ` Failures on RHEL-s390x-m64, " sergiodj+buildbot 2018-04-20 3:44 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot 2018-04-20 3:44 ` Failures on Debian-s390x-m64, " sergiodj+buildbot 2018-04-20 3:48 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2018-04-20 3:50 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-w64-mingw32, branch master *** BREAKAGE *** sergiodj+buildbot 2018-04-20 3:52 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot 2018-04-20 3:53 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot 2018-04-20 4:02 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot 2018-04-20 4:15 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2018-04-20 7:29 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot 2018-04-20 9:40 ` Failures on Fedora-x86_64-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=d27d16bfdc3f275b379793214db9bd9467b6f0f8@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).