From 84acecdda8457552bd08aa4303009b2638e96bc1 Mon Sep 17 00:00:00 2001 From: Mark Kettenis Date: Wed, 7 Jan 2004 22:12:34 +0000 Subject: * gdb.base/gdb1476.exp: Only run the tests if we can't read the memory at address 0. --- gdb/testsuite/ChangeLog | 5 +++++ gdb/testsuite/gdb.base/gdb1476.exp | 15 +++++++++++++++ 2 files changed, 20 insertions(+) diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog index 3d96343..32b6985 100644 --- a/gdb/testsuite/ChangeLog +++ b/gdb/testsuite/ChangeLog @@ -1,3 +1,8 @@ +2004-01-07 Mark Kettenis + + * gdb.base/gdb1476.exp: Only run the tests if we can't read the + memory at address 0. + 2004-01-07 Michael Chastain * 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 a65157a..ed338db 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" -- cgit v1.1