about summary refs log tree commit diff homepage
path: root/include
diff options
context:
space:
mode:
authorAlastair Reid <adreid@google.com>2020-07-30 17:02:20 +0000
committerCristian Cadar <c.cadar@imperial.ac.uk>2020-08-07 19:27:34 +0100
commit07148eeb5ea4d1c6c51e6aa5a666811ef9f50b90 (patch)
treebf296395b4bac7f3958aa146ce11a51eef84fbc6 /include
parent088fc21e12c9675161172899be5ef5051f1ae96b (diff)
downloadklee-07148eeb5ea4d1c6c51e6aa5a666811ef9f50b90.tar.gz
New intrinsic: klee_is_replay
This instrinsic detects whether the program is being executed
symbolically or concretely (i.e., using the libkleeRuntest library).

The intended usage (illustrated in the test program) is to
allow the test program to display the input values by invoking
any libraries it wants to.

This is especially valuable if you are constructing complex,
structured values and for languages like Rust (or C++) that have
rich libraries and print libraries.
For example, you might pick a symbolic value N with the
assumption "0 <= N < 10" and then pick N symbolic
values and write them to an array.
The resulting ktest file is a bit hard to understand compared with the
output of the standard print function in Rust/C++.
Diffstat (limited to 'include')
-rw-r--r--include/klee/klee.h6
1 files changed, 6 insertions, 0 deletions
diff --git a/include/klee/klee.h b/include/klee/klee.h
index 99fe15c7..fafdd55f 100644
--- a/include/klee/klee.h
+++ b/include/klee/klee.h
@@ -103,6 +103,12 @@ extern "C" {
   unsigned klee_is_symbolic(uintptr_t n);
 
 
+  /* Return true if replaying a concrete test case using the libkleeRuntime library
+   * Return false if executing symbolically in KLEE.
+   */
+  unsigned klee_is_replay();
+
+
   /* The following intrinsics are primarily intended for internal use
      and may have peculiar semantics. */