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] testsuite: Regression for foll-vfork.exp Date: Mon, 11 Jan 2016 21:25:00 -0000 [thread overview] Message-ID: <9a70630256e21a7b86344d555dbe39407e998f91@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 9a70630256e21a7b86344d555dbe39407e998f91 *** Author: Jan Kratochvil <jan.kratochvil@redhat.com> Branch: master Commit: 9a70630256e21a7b86344d555dbe39407e998f91 testsuite: Regression for foll-vfork.exp fe33faff35a8ee19db823149e764e3373e603bb9 is the first bad commit commit fe33faff35a8ee19db823149e764e3373e603bb9 Author: Simon Marchi <simon.marchi@ericsson.com> Date: Tue Dec 22 10:52:31 2015 -0500 Remove HP-UX reference in foll-vfork.exp FAIL: gdb.base/foll-vfork.exp: exec: vfork parent follow, finish after tcatch vfork: continue to vfork FAIL: gdb.base/foll-vfork.exp: exec: vfork child follow, finish after tcatch vfork: continue to vfork FAIL: gdb.base/foll-vfork.exp: exit: vfork parent follow, finish after tcatch vfork: continue to vfork FAIL: gdb.base/foll-vfork.exp: exit: vfork child follow, finish after tcatch vfork: continue to vfork It happens for plain gdb.base/foll-vfork.exp runtest on Fedora 23 x86_64. -Temporary catchpoint 2 (vforked process 24562), vfork () at ../sysdeps/unix/sysv/linux/x86_64/vfork.S:52^M +Temporary catchpoint 2 (vforked process 25345), vfork () at ../sysdeps/unix/sysv/linux/x86_64/vfork.S:52^M 52 pushq %rdi^M Current language: auto^M The current source language is "auto; currently asm".^M -(gdb) PASS: gdb.base/foll-vfork.exp: exec: vfork parent follow, finish after tcatch vfork: continue to vfork +(gdb) FAIL: gdb.base/foll-vfork.exp: exec: vfork parent follow, finish after tcatch vfork: continue to vfork -Temporary catchpoint 2 (vforked process 24629), vfork () at ../sysdeps/unix/sysv/linux/x86_64/vfork.S:52^M +Temporary catchpoint 2 (vforked process 25411), vfork () at ../sysdeps/unix/sysv/linux/x86_64/vfork.S:52^M 52 pushq %rdi^M Current language: auto^M The current source language is "auto; currently asm".^M -(gdb) PASS: gdb.base/foll-vfork.exp: exec: vfork child follow, finish after tcatch vfork: continue to vfork +(gdb) FAIL: gdb.base/foll-vfork.exp: exec: vfork child follow, finish after tcatch vfork: continue to vfork So I have reverted it and just simplified the comment. The third case is not necessary during testing but I have changed back all the 3 cases. Pedro Alves: I know it was that way before, but would you mind moving this to a helper proc. gdb/testsuite/ChangeLog 2016-01-11 Jan Kratochvil <jan.kratochvil@redhat.com> Pedro Alves <palves@redhat.com> * gdb.base/foll-vfork.exp (tcatch_vfork_then_parent_follow) (tcatch_vfork_then_child_follow_exec) (tcatch_vfork_then_child_follow_exit): Revert back DWARF vfork identification.
next reply other threads:[~2016-01-11 21:25 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-01-11 21:25 sergiodj+buildbot [this message] 2016-01-11 21:25 ` Failures on Debian-s390x-native-gdbserver-m64, branch master sergiodj+buildbot 2016-01-11 21:26 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot 2016-01-11 21:26 ` Failures on Debian-s390x-m64, " sergiodj+buildbot 2016-01-11 21:35 ` Failures on RHEL-s390x-m64, " sergiodj+buildbot 2016-01-11 21:55 ` Failures on Fedora-i686, " sergiodj+buildbot 2016-01-11 21:59 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot 2016-01-11 21:59 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2016-01-11 22:15 ` Failures on AIX-POWER7-plain, " sergiodj+buildbot 2016-01-11 22:18 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot 2016-01-11 22:34 ` Failures on Debian-i686, " sergiodj+buildbot 2016-01-11 23:14 ` Failures on Fedora-ppc64be-m64, " sergiodj+buildbot 2016-01-11 23:16 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot 2016-01-11 23:23 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot 2016-01-11 23:50 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot 2016-01-11 23:58 ` Failures on Fedora-ppc64le-m64, " sergiodj+buildbot 2016-01-11 23:58 ` Failures on Fedora-ppc64le-native-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=9a70630256e21a7b86344d555dbe39407e998f91@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).