aboutsummaryrefslogtreecommitdiffhomepage
diff options
context:
space:
mode:
authorCristian Cadar <c.cadar@imperial.ac.uk>2020-04-06 15:28:09 +0100
committerMartinNowack <2443641+MartinNowack@users.noreply.github.com>2020-06-19 18:19:53 +0100
commit88b44f7bfaa028863f63de0ecd0443bcba585d30 (patch)
treecf70267274a4aa5556cc1320d6fa186b12987cce
parent44a136227c09b403920d213f9730e911e1530487 (diff)
downloadklee-88b44f7bfaa028863f63de0ecd0443bcba585d30.tar.gz
Renamed Vararg.c to VarArg.c for consistency with the other var arg tests and reformatted comments.
-rw-r--r--test/Feature/VarArg.c (renamed from test/Feature/Vararg.c)11
1 files changed, 7 insertions, 4 deletions
diff --git a/test/Feature/Vararg.c b/test/Feature/VarArg.c
index 198da4fc..0b8b6698 100644
--- a/test/Feature/Vararg.c
+++ b/test/Feature/VarArg.c
@@ -1,9 +1,12 @@
+/* This test needs deterministic allocation with enough spacing
+ between the allocations. Otherwise, if by coincidence the
+ allocated vararg memory object is directly before another valid
+ memory object, KLEE will be able to resolve the out-of-bounds
+ access with another object and not detect the false access. This
+ will fail this test case. */
+
// RUN: %clang %s -emit-llvm %O0opt -c -g -o %t1.bc
// RUN: rm -rf %t.klee-out
-// This test needs deterministic allocation with enough spacing between the allocations.
-// Otherwise, if by coincidence the allocated vararg memory object is directly before another valid memory object,
-// KLEE will be able to resolve the out-of-bounds access with another object and not detect the false access.
-// This will fail this test case.
// RUN: %klee --output-dir=%t.klee-out --allocate-determ=true --allocate-determ-start-address=0x0 %t1.bc | FileCheck %s
// RUN: test -f %t.klee-out/test000001.ptr.err