summaryrefslogtreecommitdiff
path: root/gdb/testsuite/gdb.base/scope.exp
diff options
context:
space:
mode:
authorJeff Law <law@redhat.com>1995-08-22 19:09:39 +0000
committerJeff Law <law@redhat.com>1995-08-22 19:09:39 +0000
commitb9ba33e6f02811f1160a1209fadc0fd5401114da (patch)
tree2c2a43d88c68345ea0988bbbf1fd76c3b759144c /gdb/testsuite/gdb.base/scope.exp
parentd0c997a9aca8abef9ece6f2267e06e8fbfff488d (diff)
* gdb.base/scope.exp: xfail 'scope0.c'::filelocal_bss before run
test for PRO targets.
Diffstat (limited to 'gdb/testsuite/gdb.base/scope.exp')
-rw-r--r--gdb/testsuite/gdb.base/scope.exp6
1 files changed, 6 insertions, 0 deletions
diff --git a/gdb/testsuite/gdb.base/scope.exp b/gdb/testsuite/gdb.base/scope.exp
index a0bb7db22d..5d3cf8f70b 100644
--- a/gdb/testsuite/gdb.base/scope.exp
+++ b/gdb/testsuite/gdb.base/scope.exp
@@ -934,6 +934,12 @@ gdb_test "print 'scope0.c'::filelocal_ro" "= 201"
# gdb currently cannot access bss memory on some targets if the inferior
# is not running.
+#
+# For PA boards using monitor/remote-pa.c, the bss test is going to
+# randomly fail. We've already put remote-pa on the target stack,
+# so we actually read memory from the board. Problem is crt0.o
+# is responsible for clearing bss and that hasnt' happened yet.
+setup_xfail "hppa*-*-*pro*"
if {$gcc_compiled} then { setup_xfail "rs6000-*-*" }
send "print 'scope0.c'::filelocal_bss\n"
expect {