run_crest Some Detailed Questions

[GoogleCodeExporter]

1. The same command runs at different times, why the number of  covered 
branches is different in the end?
for example:
-desktop:~/crest/benchmarks/replace$ ../../bin/run_crest ./replace 100 -dfs
Iteration 100 (2s): covered 62 branches [12 reach funs, 148 reach branches].

then run again:

-desktop:~/crest/benchmarks/replace$ ../../bin/run_crest ./replace 100 -dfs
Iteration 100 (2s): covered 63 branches [13 reach funs, 166 reach branches].

2.With the increase of iteration times, why  the number of  covered branches 
did not increase ?
for example:
-desktop:~/crest/benchmarks/replace$ ../../bin/run_crest ./replace 100 -dfs
Iteration 0 (0s): covered 0 branches [0 reach funs, 0 reach branches].
Iteration 1 (0s): covered 51 branches [12 reach funs, 160 reach branches].
Iteration 2 (0s): covered 62 branches [13 reach funs, 166 reach branches].
Iteration 3 (0s): covered 63 branches [13 reach funs, 166 reach branches].
........
Iteration 99 (2s): covered 63 branches [13 reach funs, 166 reach branches].
Iteration 100 (2s): covered 63 branches [13 reach funs, 166 reach branches].

From Iteration 3 to Iteration 100,the number of  covered branches is unchanged.

Should CREST be able to grab all the paths, isn't it?

Could you please explain the reasons to me?
Thanks a lot !

Original issue reported on code.google.com by liuch9...@163.com on 19 Jul 2013 at 9:44

[GoogleCodeExporter]

Sorry for the slow response.  When run with the command:

    ../../bin/run_crest ./replace 100 -dfs

CREST will stop after 100 iterations, whether or not it has covered all paths.  
(And, in this case, it looks like CREST has *not* successfully covered all 
paths yet.)

Original comment by jbur...@gmail.com on 7 Feb 2014 at 5:32

• Changed state: WontFix