11CORE
22covered1.class
3- --cover location --json-ui --show-properties
3+ --cover location --json-ui --show-properties --function 'covered1.<init>'
44^EXIT=0$
55^SIGNAL=0$
66.*\"coveredLines\": \"22\",$
7- .*\"coveredLines\": \"4\",$
8- .*\"coveredLines\": \"6\",$
9- .*\"coveredLines\": \"7\",$
10- .*\"coveredLines\": \"23\",$
11- .*\"coveredLines\": \"24\",$
12- .*\"coveredLines\": \"25\",$
13- .*\"coveredLines\": \"31\",$
14- .*\"coveredLines\": \"32\",$
15- .*\"coveredLines\": \"33\",$
16- .*\"coveredLines\": \"36\",$
7+ ( .*\"coveredLines\": \"4\")|(\"coveredLines\": \"4,6,7,23-25,31-33,36\") ,$
8+ .*\"coveredLines\": \"6\"|(\"coveredLines\": \"4,6,7,23-25,31-33,36\") ,$
9+ .*\"coveredLines\": \"7\"|(\"coveredLines\": \"4,6,7,23-25,31-33,36\") ,$
10+ .*\"coveredLines\": \"23\"|(\"coveredLines\": \"4,6,7,23-25,31-33,36\") ,$
11+ .*\"coveredLines\": \"24\"|(\"coveredLines\": \"4,6,7,23-25,31-33,36\") ,$
12+ .*\"coveredLines\": \"25\"|(\"coveredLines\": \"4,6,7,23-25,31-33,36\") ,$
13+ .*\"coveredLines\": \"31\"|(\"coveredLines\": \"4,6,7,23-25,31-33,36\") ,$
14+ .*\"coveredLines\": \"32\"|(\"coveredLines\": \"4,6,7,23-25,31-33,36\") ,$
15+ .*\"coveredLines\": \"33\"|(\"coveredLines\": \"4,6,7,23-25,31-33,36\") ,$
16+ .*\"coveredLines\": \"36\"|(\"coveredLines\": \"4,6,7,23-25,31-33,36\") ,$
1717.*\"coveredLines\": \"26\",$
1818.*\"coveredLines\": \"28\",$
1919.*\"coveredLines\": \"28\",$
@@ -25,3 +25,9 @@ covered1.class
2525.*\"coveredLines\": \"35\",$
2626--
2727^warning: ignoring
28+ --
29+ The alternation between the grouped and ungrouped reporting formats for coveredLines accommodates the
30+ difference between symex-driven-lazy-loading (which currently causes jbmc to use the grouped format)
31+ and normal loading (which uses the ungrouped format).
32+ The cause of the difference appears to be symex-driven loading being more pessimistic about possible
33+ exceptions coming from callees, which in turn changes the shape of the CFG.
0 commit comments