maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/compiler-rt/test/msan/use-after-free.cc

35 lines
1.5 KiB
C++
Raw Normal View History

[MSan] Remove explicit -m64 from RUN lines. Target-specific flags should usually be configured by CMake/lit. llvm-svn: 230999
2015-03-03 03:34:27 +08:00
// RUN: %clangxx_msan -O0 %s -o %t && not %run %t >%t.out 2>&1
[msan] Fix origin of deallocated memory. MSan poisons deallocated memory but it used to give it an invalid origin value, resulting in confusing reports. This change associates deallocation stack trace with such memory. Note that MSan does not have quarantine, and use-after-free detection is very limited. llvm-svn: 190781
2013-09-16 19:03:31 +08:00
// RUN: FileCheck %s < %t.out
[MSan] Remove explicit -m64 from RUN lines. Target-specific flags should usually be configured by CMake/lit. llvm-svn: 230999
2015-03-03 03:34:27 +08:00
// RUN: %clangxx_msan -O1 %s -o %t && not %run %t >%t.out 2>&1
[msan] Fix origin of deallocated memory. MSan poisons deallocated memory but it used to give it an invalid origin value, resulting in confusing reports. This change associates deallocation stack trace with such memory. Note that MSan does not have quarantine, and use-after-free detection is very limited. llvm-svn: 190781
2013-09-16 19:03:31 +08:00
// RUN: FileCheck %s < %t.out
[MSan] Remove explicit -m64 from RUN lines. Target-specific flags should usually be configured by CMake/lit. llvm-svn: 230999
2015-03-03 03:34:27 +08:00
// RUN: %clangxx_msan -O2 %s -o %t && not %run %t >%t.out 2>&1
[msan] Fix origin of deallocated memory. MSan poisons deallocated memory but it used to give it an invalid origin value, resulting in confusing reports. This change associates deallocation stack trace with such memory. Note that MSan does not have quarantine, and use-after-free detection is very limited. llvm-svn: 190781
2013-09-16 19:03:31 +08:00
// RUN: FileCheck %s < %t.out
[MSan] Remove explicit -m64 from RUN lines. Target-specific flags should usually be configured by CMake/lit. llvm-svn: 230999
2015-03-03 03:34:27 +08:00
// RUN: %clangxx_msan -O3 %s -o %t && not %run %t >%t.out 2>&1
[msan] Fix origin of deallocated memory. MSan poisons deallocated memory but it used to give it an invalid origin value, resulting in confusing reports. This change associates deallocation stack trace with such memory. Note that MSan does not have quarantine, and use-after-free detection is very limited. llvm-svn: 190781
2013-09-16 19:03:31 +08:00
// RUN: FileCheck %s < %t.out
[MSan] Remove explicit -m64 from RUN lines. Target-specific flags should usually be configured by CMake/lit. llvm-svn: 230999
2015-03-03 03:34:27 +08:00
// RUN: %clangxx_msan -fsanitize-memory-track-origins -O0 %s -o %t && not %run %t >%t.out 2>&1
[msan] Fix origin of deallocated memory. MSan poisons deallocated memory but it used to give it an invalid origin value, resulting in confusing reports. This change associates deallocation stack trace with such memory. Note that MSan does not have quarantine, and use-after-free detection is very limited. llvm-svn: 190781
2013-09-16 19:03:31 +08:00
// RUN: FileCheck %s < %t.out && FileCheck %s --check-prefix=CHECK-ORIGINS < %t.out
[MSan] Remove explicit -m64 from RUN lines. Target-specific flags should usually be configured by CMake/lit. llvm-svn: 230999
2015-03-03 03:34:27 +08:00
// RUN: %clangxx_msan -fsanitize-memory-track-origins -O1 %s -o %t && not %run %t >%t.out 2>&1
[msan] Fix origin of deallocated memory. MSan poisons deallocated memory but it used to give it an invalid origin value, resulting in confusing reports. This change associates deallocation stack trace with such memory. Note that MSan does not have quarantine, and use-after-free detection is very limited. llvm-svn: 190781
2013-09-16 19:03:31 +08:00
// RUN: FileCheck %s < %t.out && FileCheck %s --check-prefix=CHECK-ORIGINS < %t.out
[MSan] Remove explicit -m64 from RUN lines. Target-specific flags should usually be configured by CMake/lit. llvm-svn: 230999
2015-03-03 03:34:27 +08:00
// RUN: %clangxx_msan -fsanitize-memory-track-origins -O2 %s -o %t && not %run %t >%t.out 2>&1
[msan] Fix origin of deallocated memory. MSan poisons deallocated memory but it used to give it an invalid origin value, resulting in confusing reports. This change associates deallocation stack trace with such memory. Note that MSan does not have quarantine, and use-after-free detection is very limited. llvm-svn: 190781
2013-09-16 19:03:31 +08:00
// RUN: FileCheck %s < %t.out && FileCheck %s --check-prefix=CHECK-ORIGINS < %t.out
[MSan] Remove explicit -m64 from RUN lines. Target-specific flags should usually be configured by CMake/lit. llvm-svn: 230999
2015-03-03 03:34:27 +08:00
// RUN: %clangxx_msan -fsanitize-memory-track-origins -O3 %s -o %t && not %run %t >%t.out 2>&1
[msan] Fix origin of deallocated memory. MSan poisons deallocated memory but it used to give it an invalid origin value, resulting in confusing reports. This change associates deallocation stack trace with such memory. Note that MSan does not have quarantine, and use-after-free detection is very limited. llvm-svn: 190781
2013-09-16 19:03:31 +08:00
// RUN: FileCheck %s < %t.out && FileCheck %s --check-prefix=CHECK-ORIGINS < %t.out
#include <stdlib.h>
int main(int argc, char **argv) {
int *volatile p = (int *)malloc(sizeof(int));
*p = 42;
free(p);
if (*p)
exit(0);
// CHECK: WARNING: MemorySanitizer: use-of-uninitialized-value
// CHECK: {{#0 0x.* in main .*use-after-free.cc:}}[[@LINE-3]]
[msan] Better use-after-free reports. By attaching an extra integer tag to heap origins, we are able to distinguish between uninits - created by heap allocation, - created by heap deallocation (i.e. use-after-free), - created by __msan_allocated_memory call, - etc. See https://code.google.com/p/memory-sanitizer/issues/detail?id=35. llvm-svn: 226821
2015-01-22 21:33:16 +08:00
// CHECK-ORIGINS: Uninitialized value was created by a heap deallocation
[msan] Fix origin of deallocated memory. MSan poisons deallocated memory but it used to give it an invalid origin value, resulting in confusing reports. This change associates deallocation stack trace with such memory. Note that MSan does not have quarantine, and use-after-free detection is very limited. llvm-svn: 190781
2013-09-16 19:03:31 +08:00
// CHECK-ORIGINS: {{#0 0x.* in .*free}}
// CHECK-ORIGINS: {{#1 0x.* in main .*use-after-free.cc:}}[[@LINE-9]]
return 0;
}