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] Add regression test for PR gdb/19858 (JIT code registration on attach) Date: Thu, 31 Mar 2016 19:43:00 -0000 [thread overview] Message-ID: <85af34ee0211eedf8d30a5c44dfc59dddf8b512a@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 85af34ee0211eedf8d30a5c44dfc59dddf8b512a *** Author: Pedro Alves <palves@redhat.com> Branch: gdb-7.11-branch Commit: 85af34ee0211eedf8d30a5c44dfc59dddf8b512a Add regression test for PR gdb/19858 (JIT code registration on attach) This test would fail without the previous gdb/jit.c fix: (gdb) attach 23031 Attaching to program: .../build/gdb/testsuite/outputs/gdb.base/jit/jit-main, process 23031 [...] 207 WAIT_FOR_GDB; i = 0; /* gdb break here 1 */ (gdb) PASS: gdb.base/jit.exp: attach: one_jit_test-2: attach set var wait_for_gdb = 0 (gdb) PASS: gdb.base/jit.exp: attach: one_jit_test-2: set var wait_for_gdb = 0 info function ^jit_function All functions matching regular expression "^jit_function": (gdb) FAIL: gdb.base/jit.exp: attach: one_jit_test-2: info function ^jit_function gdb/testsuite/ChangeLog: 2016-03-31 Pedro Alves <palves@redhat.com> PR gdb/19858 * gdb.base/jit-main.c: Include unistd.h. (ATTACH): Define to 0 if not already defined. (wait_for_gdb, mypid): New globals. (WAIT_FOR_GDB): New macro. (MAIN): Set an alarm. Store the process's pid. Wait for GDB at some breakpoint locations. * gdb.base/jit.exp (clean_reattach, continue_to_test_location): New procedures. (one_jit_test): Add REATTACH parameter, and handle it. Use continue_to_test_location. (top level): Test attach, and adjusts calls to one_jit_test.
next reply other threads:[~2016-03-31 19:41 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-03-31 19:43 sergiodj+buildbot [this message] 2016-03-31 20:02 ` Failures on RHEL-s390x-m64, branch gdb-7.11-branch sergiodj+buildbot 2016-03-31 22:19 ` Failures on AIX-POWER7-plain, " sergiodj+buildbot 2016-03-31 23:03 ` Failures on Debian-i686, " sergiodj+buildbot 2016-03-31 23:25 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot 2016-04-01 0:06 ` Failures on Fedora-i686, " sergiodj+buildbot 2016-04-01 0:14 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot 2016-04-01 0:27 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2016-04-01 0:28 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2016-04-01 0:30 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2016-04-01 0:53 ` Failures on Debian-x86_64-m64, " sergiodj+buildbot 2016-04-01 0:54 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot 2016-04-01 1:07 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot 2016-04-01 4:12 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot 2016-04-01 8:26 ` Failures on Fedora-ppc64be-cc-with-index, " sergiodj+buildbot 2016-04-01 8:47 ` Failures on Fedora-ppc64be-m64, " sergiodj+buildbot 2016-04-01 9:06 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot 2016-04-01 9:27 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot 2016-04-01 15:44 ` Failures on Fedora-ppc64le-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=85af34ee0211eedf8d30a5c44dfc59dddf8b512a@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).