Hi Martin,
Done. Thank you again.
Thanks,
Daniel
*
Daniel Schwartz - ds3...@columbia.edu
M.S. Candidate, Computer Science
Columbia University, 2018
https://www.linkedin.com/in/danielschwartz2/
On Thu, Feb 22, 2018 at 4:12 PM, Martin Nowack wrote:
> Hi Danie
Hi Daniel,
This is strange - hanging at __libc_fork() with 100% cpu load should not happen.
Can you open a bug report on GitHub and we try to continue there?
* And could you add there what system you have (Linux distribution)
* Add the code around: __libc_fork () at
../nptl/sysdeps/unix/sysv/li
Hi,
I looked again to see if I missed a child process of this fork but didn't.
I provided all the information I have below:
When I check the running processes, I see:
9667: klee-1.4.0_build_dir/bin/klee --libc=uclibc --posix-runtime
--simplify-sym-indices --write-cvcs --write-cov --output-module
Thank you Martin.
Here is the backtrace from gdb:
(gdb) bt
#0 0x2b5816da8e34 in __libc_fork () at
../nptl/sysdeps/unix/sysv/linux/x86_64/../fork.c:130
#1 0x0080f0b8 in runAndGetCexForked (timeout=0,
hasSolution=@0x7fffb2ea1cbf: false, values=std::vector of length 0,
capacity 0, objec
Hi Daniel,
KLEE is not crashing but the timeout (--max-time=10800) is reached.
The thing what happens in your case is that the KLEE watchdog process tries to
kill KLEE vie attaching to it using gdb. So KLEE does not terminate or does not
have enough time to terminate.
It could be that KLEE is w
