summaryrefslogtreecommitdiffstats
path: root/compiler-rt/test/fuzzer/buffer-overflow-on-input.test
diff options
context:
space:
mode:
authorGeorge Karpenkov <ekarpenkov@apple.com>2018-05-11 21:29:53 +0000
committerGeorge Karpenkov <ekarpenkov@apple.com>2018-05-11 21:29:53 +0000
commit669375814c0aef15b7f018ccd9e91b3ec9883efc (patch)
treeff68056d9e6fe1e4d19e18f4cbdff906b8a5ece6 /compiler-rt/test/fuzzer/buffer-overflow-on-input.test
parentfa57519e317f05ba8c01814062125db1f4793829 (diff)
downloadbcm5719-llvm-669375814c0aef15b7f018ccd9e91b3ec9883efc.tar.gz
bcm5719-llvm-669375814c0aef15b7f018ccd9e91b3ec9883efc.zip
[libFuzzer] [NFC] Split fuzzer.test into smaller tests
Keeping fuzzer.test together as a gigantic test has no advantages and multiple disadvantages: - Worse test parallelization (fuzzer.test is always blocking the test run on a machine with many cores) - Debugging test failures is made more difficult (not clear what fails from fuzzer.test failing) - Makes porting tests to new platforms more difficult (whenever fuzzer.test fails have to inspect the output to figure out what is going on, and then restart all of it) - Hides dead code (in our case, "Done1000000" FileCheck variable was never used, DISABLED: not %t-UninstrumentedTest-Uninstrumented was never compiled, and there was small amount of duplication vs. simple-cmp.test) - Makes correspondence between LIT .test files and .cpp files less straightforward Differential Revision: https://reviews.llvm.org/D46557 llvm-svn: 332145
Diffstat (limited to 'compiler-rt/test/fuzzer/buffer-overflow-on-input.test')
-rw-r--r--compiler-rt/test/fuzzer/buffer-overflow-on-input.test5
1 files changed, 5 insertions, 0 deletions
diff --git a/compiler-rt/test/fuzzer/buffer-overflow-on-input.test b/compiler-rt/test/fuzzer/buffer-overflow-on-input.test
new file mode 100644
index 00000000000..6e40b75d70b
--- /dev/null
+++ b/compiler-rt/test/fuzzer/buffer-overflow-on-input.test
@@ -0,0 +1,5 @@
+RUN: %cpp_compiler %S/BufferOverflowOnInput.cpp -o %t-BufferOverflowOnInput
+
+RUN: not %run %t-BufferOverflowOnInput 2>&1 | FileCheck %s --check-prefix=OOB
+OOB: AddressSanitizer: heap-buffer-overflow
+OOB: is located 0 bytes to the right of 3-byte region
OpenPOWER on IntegriCloud