From: Mark Kettenis <kettenis@gnu.org>
Date: Wed, 7 Jan 2004 22:12:34 +0000 (+0000)
Subject: * gdb.base/gdb1476.exp: Only run the tests if we can't read the
X-Git-Url: http://git.osdn.net/view?a=commitdiff_plain;h=26015b76e3ad6e92a880b5bf2380c4fbb6c01db3;p=pf3gnuchains%2Fpf3gnuchains3x.git

* gdb.base/gdb1476.exp: Only run the tests if we can't read the
memory at address 0.
---

diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog
index 3d96343d1b..32b6985163 100644
--- a/gdb/testsuite/ChangeLog
+++ b/gdb/testsuite/ChangeLog
@@ -1,3 +1,8 @@
+2004-01-07  Mark Kettenis  <kettenis@gnu.org>
+
+	* gdb.base/gdb1476.exp: Only run the tests if we can't read the
+	memory at address 0.
+
 2004-01-07  Michael Chastain  <mec.gnu@mindspring.com>
 
 	* gdb.stabs/weird.exp: Use hp_cc_compiler and hp_aCC_compiler
diff --git a/gdb/testsuite/gdb.base/gdb1476.exp b/gdb/testsuite/gdb.base/gdb1476.exp
index a65157a8d4..ed338db9ee 100644
--- a/gdb/testsuite/gdb.base/gdb1476.exp
+++ b/gdb/testsuite/gdb.base/gdb1476.exp
@@ -48,6 +48,21 @@ if ![runto_main] then {
     gdb_suppress_tests
 }
 
+# If we can examine what's at memory address 0, it is possible that we
+# could also execute it.  This could pobably make us run away,
+# executing random code, which could have all sorts of ill effects,
+# especially on targets without an MMU.  Don't run the tests in that
+# case.
+
+send_gdb "x 0\n"
+gdb_expect {
+    -re "0x0:.*Error accessing memory address 0x0.*$gdb_prompt $" { }
+    -re ".*$gdb_prompt $" {
+	untested "Memory at address 0 is possibly executable"
+	return
+    }
+}
+
 gdb_test "continue" "Program received signal SIGSEGV.*" \
 	"continue to null pointer call"