diff options
| -rw-r--r-- | gdb/testsuite/ChangeLog | 5 | ||||
| -rw-r--r-- | gdb/testsuite/gdb.base/testenv.exp | 8 |
2 files changed, 13 insertions, 0 deletions
diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog index 6ed0407..866593e 100644 --- a/gdb/testsuite/ChangeLog +++ b/gdb/testsuite/ChangeLog @@ -1,5 +1,10 @@ 2011-11-30 Ulrich Weigand <uweigand@de.ibm.com> + * gdb.base/testenv.exp: Skip on remote targets. Unset global + environment variable after test completed. + +2011-11-30 Ulrich Weigand <uweigand@de.ibm.com> + * gdb.base/solib-nodir.exp: Skip if remote target. * gdb.base/gdb.fortran.exp: Use shlib= flag when linking main application. Call gdb_load_shlibs. diff --git a/gdb/testsuite/gdb.base/testenv.exp b/gdb/testsuite/gdb.base/testenv.exp index ad39f14..dae35b6 100644 --- a/gdb/testsuite/gdb.base/testenv.exp +++ b/gdb/testsuite/gdb.base/testenv.exp @@ -22,6 +22,10 @@ if $tracelevel then { strace $tracelevel } +# There's no support for passing environment variables in the remote protocol. +if { [is_remote target] } { + return 0 +} set testfile "testenv" set srcfile ${testfile}.c @@ -119,3 +123,7 @@ gdb_test "continue" \ "Test with TEST_GDB_GLOBAL unset" gdb_exit + +# Clear environment in case we're doing multiple runs +unset env(TEST_GDB_GLOBAL) + |