public inbox for gdb-testers@sourceware.org help / color / mirror / Atom feed
From: sergiodj+buildbot@redhat.com To: gdb-testers@sourceware.org Subject: [binutils-gdb] btrace: async Date: Fri, 18 Sep 2015 14:30:00 -0000 [thread overview] Message-ID: <a6b5be76f94664406def040d79ac8bc4d4aa8bd0@gdb-build> (raw) *** TEST RESULTS FOR COMMIT a6b5be76f94664406def040d79ac8bc4d4aa8bd0 *** Author: Markus Metzger <markus.t.metzger@intel.com> Branch: master Commit: a6b5be76f94664406def040d79ac8bc4d4aa8bd0 btrace: async The record btrace target runs synchronous with GDB. That is, GDB steps resumed threads in record btrace's to_wait method. Without GDB calling to_wait, nothing happens 'on the target'. Check for further expected events in to_wait before reporting the current event and mark record btrace's async event handler in async mode. gdb/ * record-btrace.c (record_btrace_maybe_mark_async_event): New. (record_btrace_wait): Call record_btrace_maybe_mark_async_event.
next reply other threads:[~2015-09-18 14:06 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-09-18 14:30 sergiodj+buildbot [this message] 2015-09-18 14:29 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot 2015-09-18 17:44 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot 2015-09-18 17:58 ` Failures on Debian-s390x-m64, " sergiodj+buildbot 2015-09-18 18:04 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot 2015-09-18 18:54 ` Failures on AIX-POWER7-plain, " sergiodj+buildbot 2015-09-18 21:26 ` Failures on Fedora-i686, " sergiodj+buildbot 2015-09-18 21:36 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2015-09-18 21:38 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2015-09-18 21:46 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2015-09-18 22:02 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot 2015-09-18 22:51 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot 2015-09-19 3:35 ` Failures on Fedora-ppc64be-m64, " sergiodj+buildbot 2015-09-19 4:01 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot 2015-09-19 5:50 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot 2015-09-19 6:19 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot 2015-09-19 11:15 ` Failures on Debian-i686-native-gdbserver, " sergiodj+buildbot 2015-09-19 12:52 ` Failures on Debian-x86_64-native-extended-gdbserver-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=a6b5be76f94664406def040d79ac8bc4d4aa8bd0@gdb-build \ --to=sergiodj+buildbot@redhat.com \ --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).