> 1) printf is run concretely by default (you can add -DKLEE_SYM_PRINTF when
> compiling KLEE's uclibc to change this)
Ok, this is not a major issue, printf can be replaced by fprintf (assuming the
latter is supported).
> 2) you should only use —sym-sdout if you need to symbolically analyze
Hi Eduardo,
Indeed, we need better documentation here. But in a nutshell:
1) printf is run concretely by default (you can add -DKLEE_SYM_PRINTF
when compiling KLEE's uclibc to change this)
2) you should only use —sym-sdout if you need to symbolically analyze
the contents of stdout,
