From: Don Breazeal <donb@codesourcery.com>
To: <gdb-patches@sourceware.org>
Subject: [PATCH 3/3] Disable exec-dependent follow fork tests for remote
Date: Fri, 22 May 2015 18:56:00 -0000 [thread overview]
Message-ID: <1432320931-1550-4-git-send-email-donb@codesourcery.com> (raw)
In-Reply-To: <1432320931-1550-1-git-send-email-donb@codesourcery.com>
The native-extended-gdbserver target now supports fork events and
follow fork, but it does not yet support exec events. Some of the
tests in gdb.base/foll-vfork.exp depend on exec events. This patch
disables those tests for gdbserver targets. We can re-enable these
once the exec event support goes in.
OK?
--Don
gdb/testsuite/
2015-05-22 Don Breazeal <donb@codesourcery.com>
* gdb.base/foll-vfork.exp (main): Disable exec-dependent
tests for remote targets by checking is_target_gdbserver.
---
gdb/testsuite/gdb.base/foll-vfork.exp | 28 ++++++++++++++++------------
1 file changed, 16 insertions(+), 12 deletions(-)
diff --git a/gdb/testsuite/gdb.base/foll-vfork.exp b/gdb/testsuite/gdb.base/foll-vfork.exp
index 78c5cc8..26d7afd 100644
--- a/gdb/testsuite/gdb.base/foll-vfork.exp
+++ b/gdb/testsuite/gdb.base/foll-vfork.exp
@@ -524,18 +524,22 @@ with_test_prefix "check vfork support" {
check_vfork_catchpoints
}
-# Follow parent and follow child vfork tests with a child that execs.
-with_test_prefix "exec" {
- # These are tests of gdb's ability to follow the parent of a Unix
- # vfork system call. The child will subsequently call a variant
- # of the Unix exec system call.
- do_vfork_and_follow_parent_tests
-
- # These are tests of gdb's ability to follow the child of a Unix
- # vfork system call. The child will subsequently call a variant
- # of a Unix exec system call.
- #
- do_vfork_and_follow_child_tests_exec
+if { ![target_is_gdbserver] } {
+ # Follow parent and follow child vfork tests with a child that execs.
+ with_test_prefix "exec" {
+ # These are tests of gdb's ability to follow the parent of a Unix
+ # vfork system call. The child will subsequently call a variant
+ # of the Unix exec system call.
+ do_vfork_and_follow_parent_tests
+
+ # These are tests of gdb's ability to follow the child of a Unix
+ # vfork system call. The child will subsequently call a variant
+ # of a Unix exec system call.
+ #
+ do_vfork_and_follow_child_tests_exec
+ }
+} else {
+ untested "vfork with exec: exec events not supported for remote"
}
# Switch to test the case of the child exiting. We can't use
--
1.8.1.1
next prev parent reply other threads:[~2015-05-22 18:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 18:55 [PATCH 0/3] Extended-remote follow-fork cleanups Don Breazeal
2015-05-22 18:55 ` [PATCH 1/3] Make remote follow fork 'Detaching' message match native Don Breazeal
2015-05-23 11:18 ` Pedro Alves
2015-05-22 18:55 ` [PATCH 2/3] Initialize last_resume_kind for remote fork child Don Breazeal
2015-05-23 12:05 ` Pedro Alves
2015-05-22 18:56 ` Don Breazeal [this message]
2015-05-23 12:11 ` [PATCH 3/3] Disable exec-dependent follow fork tests for remote Pedro Alves
2015-05-23 12:14 ` Pedro Alves
2015-05-28 22:12 ` [commit][PATCH 1/3] Make remote follow fork 'Detaching' message match native Don Breazeal
2015-05-28 22:13 ` [commit][PATCH 2/3] Initialize last_resume_kind for remote fork child Don Breazeal
2015-05-28 22:13 ` [commit][PATCH 3/3] Disable exec-dependent follow vfork tests for remote Don Breazeal
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=1432320931-1550-4-git-send-email-donb@codesourcery.com \
--to=donb@codesourcery.com \
--cc=gdb-patches@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