This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
[commit] restore testing of source foo.py if python not configured in
- From: Doug Evans <xdje42 at gmail dot com>
- To: gdb-patches at sourceware dot org
- Date: Sat, 23 Nov 2013 15:11:42 -0800
- Subject: [commit] restore testing of source foo.py if python not configured in
- Authentication-results: sourceware.org; auth=none
Hi.
I happened to notice this.
We early exit if python is not configured in, and then follow that up
with a test to verify proper handling of "source foo.py" if python
is not configured in. Oops.
Tested on amd64-linux, with/without python.
Committed.
2013-11-23 Doug Evans <xdje42@gmail.com>
* gdb.python/python.exp: Don't call skip_python_tests, we still want
to test some things in the case where python is not configured in.
diff --git a/gdb/testsuite/gdb.python/python.exp b/gdb/testsuite/gdb.python/python.exp
index b0faf9a..69ba900 100644
--- a/gdb/testsuite/gdb.python/python.exp
+++ b/gdb/testsuite/gdb.python/python.exp
@@ -30,9 +30,8 @@ gdb_exit
gdb_start
gdb_reinitialize_dir $srcdir/$subdir
-# Skip all tests if Python scripting is not enabled.
-if { [skip_python_tests] } { continue }
-
+# Do this instead of the skip_python_check.
+# We want to do some tests when Python is not present.
gdb_test_multiple "python print (23)" "verify python support" {
-re "not supported.*$gdb_prompt $" {
unsupported "python support is disabled"