Hello, I am currently working on a project to verify states that end due to errors such as "memory error: out of bound pointer". Currently, I am trying to extract some information about these states, and the most information I am able to extract is the instruction log from replaying only the seed file, using the options --debug-print-instructions and --only-seed --seed-file .
Is there any way to extract more details? While running an application with a seed input. Also, for the debug-print-instructions=all:stderr is there any way to restrict Klee from printing all the instructions inside the libraries? It takes an insane amount of time looping inside the runtime setup code as well as library functions such as sprintf etc. (Note that at this point - I am replaying an input, which I know leads to an error, so it's mostly "pre-constrained symbolic execution")
_______________________________________________ klee-dev mailing list klee-dev@imperial.ac.uk https://mailman.ic.ac.uk/mailman/listinfo/klee-dev
