Hi, I have a few questions about computing the coverage.
I was wondering if there is a way to use run.istats to generate the coverage just for the interesting source files (i.e., not for the library files). If this is possible, it wouldn't be necessary to replay the test cases and use gcov to get the coverage results. In your experience, does run.istats reliably show the coverage information (or the uncovered lines) when running with klee --optimize? I tried with echo.bc and did not see what I was expecting, kcachegrind did not display any uncovered lines in echo.c, as it was supposed to. Finally, since Klee generates statistics when it covers new lines, would it be possible to take the information from run.istats and view what coverage results were obtained at each moment of time? (Something like an iterative coverage monitor). Thanks, Cristi
