e595e1ade0
Init-order and use-after-return modes can currently be enabled by runtime flags. use-after-scope mode is not really working at the moment. The only problem I see is that users won't be able to disable extra instrumentation for init-order and use-after-scope by a top-level Clang flag. But this instrumentation was implicitly enabled for quite a while and we didn't hear from users hurt by it. llvm-svn: 210924
30 lines
1.2 KiB
C++
30 lines
1.2 KiB
C++
// Test for blacklist functionality of initialization-order checker.
|
|
|
|
// RUN: %clangxx_asan -O0 %s %p/Helpers/initialization-blacklist-extra.cc\
|
|
// RUN: %p/Helpers/initialization-blacklist-extra2.cc \
|
|
// RUN: -fsanitize-blacklist=%p/Helpers/initialization-blacklist.txt -o %t
|
|
// RUN: env ASAN_OPTIONS=check_initialization_order=true %run %t 2>&1
|
|
// RUN: %clangxx_asan -O1 %s %p/Helpers/initialization-blacklist-extra.cc\
|
|
// RUN: %p/Helpers/initialization-blacklist-extra2.cc \
|
|
// RUN: -fsanitize-blacklist=%p/Helpers/initialization-blacklist.txt -o %t
|
|
// RUN: env ASAN_OPTIONS=check_initialization_order=true %run %t 2>&1
|
|
// RUN: %clangxx_asan -O2 %s %p/Helpers/initialization-blacklist-extra.cc\
|
|
// RUN: %p/Helpers/initialization-blacklist-extra2.cc \
|
|
// RUN: -fsanitize-blacklist=%p/Helpers/initialization-blacklist.txt -o %t
|
|
// RUN: env ASAN_OPTIONS=check_initialization_order=true %run %t 2>&1
|
|
|
|
// Function is defined in another TU.
|
|
int readBadGlobal();
|
|
int x = readBadGlobal(); // init-order bug.
|
|
|
|
// Function is defined in another TU.
|
|
int accessBadObject();
|
|
int y = accessBadObject(); // init-order bug.
|
|
|
|
int readBadSrcGlobal();
|
|
int z = readBadSrcGlobal(); // init-order bug.
|
|
|
|
int main(int argc, char **argv) {
|
|
return argc + x + y + z - 1;
|
|
}
|