Age | Commit message (Collapse) | Author |
|
|
|
|
|
C++ static destructors are currently not supported for newer LLVM version.
Keep older LLVM version until issue is fixed.
|
|
Linking with Z3 might fail if Z3 is built with UBSan as parts of Z3 are
written in C++.
Check explicitly with a C++ compiler.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* Just target x86 as architecture
* do not build tests for clang
* use optimized tablegen
* only build required tools and libraries that are needed by KLEE
|
|
* re-use an existing LLVM directory if possible
* only export the bitcode files
|
|
Clang is just a compiler and can be provided by system-specific packages.
|
|
Any clang is fine as long as it is the right version.
The current assumption is that it is suffixed with version.
|
|
These arguments are not required and let the link process fail.
Instead, clang(++) should be used as a linker and it will take care of
linking with the correct libraries.
|
|
Don't keep the docker instance for detecting the system around to
avoid stale terminated containers.
|
|
The build support for libc++ for LLVM 3.8 is broken.
It's not worth fixing.
|
|
Use newer LLVM version 9.0 instead of 6.0.
Update to newer Ubuntu base image.
|
|
|
|
This is in preparation for LLVM 11 as the llvm:CallSite class has been
removed.
|
|
|
|
we have encountered
|
|
|
|
|
|
klee-zesti takes concrete arguments, files and stdin of the program under tests
converts them to a seed and then runs klee with that seed. This emulates the interface of ZESTI.
|
|
Argument `-y` has been removed from the upload script.
https://github.com/codecov/codecov-bash/commit/c2f935a0dd0590d20296e95a759782e32b311b34
But `.codecov.yml` is now supported
|
|
|
|
|
|
The new build script doesn't use that facility anymore.
Remove it to avoid interfirence with ccache.
|
|
Recently, Homebrew packages can be installed via `.travis.yml`.
Use this functionality instead of calling brew directly.
Hopefully works around the build issue.
|
|
|
|
|
|
The previous version left unnecessary intermediate nodes behind, sometimes
leading to very long paths in the tree.
|
|
|
|
- If an unknown intrinsic appears in the bitcode file,
it is reported but execution can proceed.
- If an unknown intrinsic is encountered during execution of some path,
- the intrinsic is reported
- this path is treated as an error
- execution of other paths can proceed
To be more precise, there is a list of "known unknown intrinsics".
Intrinsics not on this list will prevent execution.
|
|
This is a thread-local version of __cxa_atexit (but, in the absence
of threads, it is sufficient to just call __cxa_atexit).
The test is based on the existing test for atexit in
test/Runtime/Uclibc/2008-03-04-libc-atexit-uses-dso-handle.c
The motivation for adding this function is to support the Rust standard
library that calls __cxa_thread_atexit_impl.
This function is usually a weak symbol but, in KLEE, this behaves like a call
to an unknown function and chaos ensues.
Worse, it happens just as the program is cleanly shutting itself down,
so programs that are cleanly exiting crash with the wrong message.
|
|
outputting wrong data.
When KLEE crashes, it produces an empty info file, so it is not enough to check for the existence of an info file.
Previously, table columns would mismatch and return data labeled with the wrong directory names.
|
|
|
|
|
|
This change allows KLEE to be configured to use the LLVM version
that comes with the Rust compiler instead of a standard version.
e.g., one might configure with
-DLLVM_CONFIG_BINARY=${RUST_SRC}/build/x86_64-unknown-linux-gnu/llvm/bin/llvm-config
For which typical output might be
10.0.1-rust-dev
|
|
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++.
|
|
|
|
* move global theRNG into Executor
* pass theRNG via ctor to searchers
* remove some type warnings from RNG.cpp
Fixes #1023.
|
|
|
|
|
|
This constructor has been a hack and was wrongly used, use ConstraintManager instead.
Allow copy-constructing states only via `ExecutionState::branch()` call.
|
|
Decouple ExecutionState from TimingSolver
Instead of providing an execution state to the timing solver use a set of
constraints and an additional object for metadata.
Fixes:
* correct accounting of metadata to a specific state
* accounting of all solver invocations (e.g. solver-getRange was not
accounted)
* allows to invoke the solver without a state (avoids costly copying of
states/constraints)
|
|
|
|
|
|
|