[klee-dev] Best practice to run chmod from GNU Coreutils 6.10
Hi all, I use klee docker image 1.3.0 to run experiments on GNU Coreutils chmod.bc with arguments here. But my docker container falls into crash due to this program changes my privilege symbolically and I cannot find any way to repair the container because it cannot start as shown below: /bin/bash:error while loading libraries: libtinfo.so.5: cannot open shared object file: Permission denied. Do you have any idea to run this program? Thanks, Yushan___ klee-dev mailing list klee-dev@imperial.ac.uk https://mailman.ic.ac.uk/mailman/listinfo/klee-dev
[klee-dev] Question on Klee-array Virtual Machine
Hi all, I downloaded the virtual machine for ISSTA'17 paper here, but it requires username and password to login. Does anyone know the correct information needed to run the machine? And where could I find the instructions to compile Binutils 2.27 correctly as *.bc? I try to follow the instructions for Coreutils, but after the "make" command, the tutorial didn't work anymore. I appreciate any possible help. Thank you all, Yushan___ klee-dev mailing list klee-dev@imperial.ac.uk https://mailman.ic.ac.uk/mailman/listinfo/klee-dev
Re: [klee-dev] KLEE: ERROR: error loading program 'pallin.c':Invalid bitcode signature
It's horrible if you try to install KLEE on Mac OSX machines, the default compile chaining is customized by Apple and it's hard to manage your environment. Please try using the docker image by following the tutorial on the official website. And also you should use *.bc file to feed into KLEE. I recommend this tutorial for you, good luck! Yushan -- Original -- From: "Dan Liew"; Date: Thu, Oct 12, 2017 04:51 PM To: "Chengyu Zhang" ; Cc: "klee-dev" ; Subject: Re: [klee-dev] KLEE: ERROR: error loading program 'pallin.c':Invalid bitcode signature On 12 October 2017 at 08:49, Chengyu Zhang wrote: > Maybe you should run KLEE on .bc file generated by Clang rather than .c > file. To add to that you can't use "Apple Clang". You need to use a version of Clang that uses the same version of LLVM that KLEE was built with. In your case your version of KLEE uses LLVM 3.4 so you need to use Clang 3.4. At a glance it looks like you're using Docker to run KLEE. So you should probably invoke Clang inside the Docker container to build your code. ___ klee-dev mailing list klee-dev@imperial.ac.uk https://mailman.ic.ac.uk/mailman/listinfo/klee-dev___ klee-dev mailing list klee-dev@imperial.ac.uk https://mailman.ic.ac.uk/mailman/listinfo/klee-dev