Open mrigger opened 5 years ago
For the memory safety violation, the bounds associated with the access seems to indicate that it is out-of-bounds access. It needs to be debugged to figure if it is a true out-of-bounds access or a false violation.
To handle the second issue, the pass needs to be updated to handle atomic instructions in the LLVM IR. Although it is on my todo list, I don't have anyone working on it right now.
Hi, I'm trying to run Softbound+CETS on the Cicro benchmark suite. During run time, Softbound signals a memory safety violation for every benchmark, which is not the case for other tools (such as ASan, MSan, and Valgrind). Here is one example output:
Additionally, a number of benchmarks do not compile due to various issues, such as the ones outlined below:
Do you have any advice on how to address these issues?