This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
[patch] Skip gdb.threads/execl.exp on remote target
- From: Yao Qi <yao at codesourcery dot com>
- To: gdb-patches at sourceware dot org
- Date: Fri, 17 Jun 2011 17:26:43 +0800
- Subject: [patch] Skip gdb.threads/execl.exp on remote target
As far as I know, exec event is not handled in gdbserver or in remote
debugging, so this patch is to skip gdb.threads/execl.exp on remote target.
The condition checking in my patch is "{ [is_remote target] }", instead
of "{ [is_remote target] || ![isnative] }", which is widely used
elsewhere, because "![isnative]" can be regarded as a subset of
"is_remote target". I can't think of a case that non-native debugger
works with non-remote board. Am I missing something?
--
Yao (éå)
2011-06-17 Yao Qi <yao@codesourcery.com>
gdb/testsuite/
* gdb.threads/execl.exp: Skip on remote target.
diff --git a/gdb/testsuite/gdb.threads/execl.exp b/gdb/testsuite/gdb.threads/execl.exp
index cd4a801..d1f7e74 100644
--- a/gdb/testsuite/gdb.threads/execl.exp
+++ b/gdb/testsuite/gdb.threads/execl.exp
@@ -15,6 +15,9 @@
# Test handling of threads across an execl.
+if { [is_remote target] } then {
+ continue
+}
# Original image, loads a thread library.
set testfile "execl"