squiid/llvm
1
0
Fork 0
Code Issues Pull requests Activity

Further relax checks in asan-symbolize-bad-path.cpp

Browse source 
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
This commit is contained in:
Alexander Richardson 2019-08-28 18:37:53 +00:00
parent f7a544bca8
commit 83d2f0e799
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
compiler-rt/test/asan/TestCases/Posix/asan-symbolize-bad-path.cpp
View file

@ -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() {