[asan] Implement SEGV read vs write detection for ARM and AArch64.

git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@260163 91177308-0d34-0410-b5e6-96231b3b80d8

1 files changed, 12 insertions, 4 deletions

diff --git a/test/asan/TestCases/Linux/segv_read_write.c b/test/asan/TestCases/Linux/segv_read_write.c
index db6726cd3..d5a62c66d 100644
--- a/test/asan/TestCases/Linux/segv_read_write.c
+++ b/test/asan/TestCases/Linux/segv_read_write.c
@@ -1,16 +1,24 @@
-// RUN: %clangxx_asan -O0 %s -o %t
+// RUN: %clangxx_asan -std=c++11 -O0 %s -o %t
 // RUN: not %run %t       2>&1 | FileCheck %s --check-prefix=READ
 // RUN: not %run %t write 2>&1 | FileCheck %s --check-prefix=WRITE
-// REQUIRES: x86_64-supported-target
+// UNSUPPORTED: powerpc64,mips
+
+#include <sys/mman.h>
 
 static volatile int sink;
 __attribute__((noinline)) void Read(int *ptr) { sink = *ptr; }
 __attribute__((noinline)) void Write(int *ptr) { *ptr = 0; }
 int main(int argc, char **argv) {
+  // Writes to shadow are detected as reads from shadow gap (because of how the
+  // shadow mapping works). This is kinda hard to fix. Test a random address in
+  // the application part of the address space.
+  void *volatile p =
+      mmap(nullptr, 4096, PROT_READ, MAP_PRIVATE | MAP_ANONYMOUS, 0, 0);
+  munmap(p, 4096);
   if (argc == 1)
-    Read((int *)0);
+    Read((int *)p);
   else
-    Write((int *)0);
+    Write((int *)p);
 }
 // READ: AddressSanitizer: SEGV on unknown address
 // READ: The signal is caused by a READ memory access.