From 83d2f0e7993a376c5ffb65e5760e58e72d27daee Mon Sep 17 00:00:00 2001 From: Alexander Richardson Date: Wed, 28 Aug 2019 18:37:53 +0000 Subject: [PATCH] Further relax checks in asan-symbolize-bad-path.cpp It turns out that the DarwinSymbolizer does not print the "in" part for invalid files but instead prints #0 0xabcdabcd (.../asan-symbolize-bad-path.cpp.tmp/bad/path:i386+0x1234) This tests is only checking that asan_symbolize.py doesn't hang or crash, so further relax the checks to ensure that the test passes on macOS. llvm-svn: 370243 --- .../test/asan/TestCases/Posix/asan-symbolize-bad-path.cpp | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/compiler-rt/test/asan/TestCases/Posix/asan-symbolize-bad-path.cpp b/compiler-rt/test/asan/TestCases/Posix/asan-symbolize-bad-path.cpp index d416838726ac..c53a932a2e9e 100644 --- a/compiler-rt/test/asan/TestCases/Posix/asan-symbolize-bad-path.cpp +++ b/compiler-rt/test/asan/TestCases/Posix/asan-symbolize-bad-path.cpp @@ -2,13 +2,13 @@ // path. // RUN: echo '#0 0xabcdabcd (%t/bad/path+0x1234)' | %asan_symbolize | FileCheck %s -check-prefix CHECK-BAD-FILE // Note: can't check for "0xabcdabcd in ?? ??:0" since DarwinSymbolizer will print the file even if it doesn't exist. -// CHECK-BAD-FILE: #0 0xabcdabcd in +// CHECK-BAD-FILE: #0 0xabcdabcd // CHECK-BAD-FILE-EMPTY: // Also test that asan_symbolize doesn't assert on an invalid address with a valid file: // RUN: %clangxx_asan -O0 %s -o %t // RUN: echo '#0 0xabcdabcd (%t+0xabcdabcd)' | %asan_symbolize | FileCheck %s -check-prefix CHECK-BAD-ADDR -// CHECK-BAD-ADDR: #0 0xabcdabcd in +// CHECK-BAD-ADDR: #0 0xabcdabcd // CHECK-BAD-ADDR-EMPTY: int main() {