1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
|
CORE
main.c
--apply-loop-contracts _ --no-standard-checks
^EXIT=10$
^SIGNAL=0$
^\[main\.\d+\] .* Check loop invariant before entry: SUCCESS$
^\[main\.\d+\] .* Check that loop invariant is preserved: SUCCESS$
^\[main.assigns.\d+\] .* Check that i is assignable: SUCCESS$
^\[main.assigns.\d+\] .* Check that data\[(\(signed long (long )?int\))?1\] is assignable: SUCCESS$
^\[main\.assertion\.\d+\] .* assertion data\[1\] == 0 \|\| data\[1\] == 1: FAILURE$
^\[main\.assertion\.\d+\] .* assertion data\[4\] == 0: SUCCESS$
^VERIFICATION FAILED$
--
--
Test case related to issue #6020: it checks that dynamically allocated arrays
are correctly havoced when enforcing loop invariant contracts.
The `data[1] == 0 || data[1] == 1` assertion is expected to fail since `data[1]`
is havoced and the invariant does not reestablish the value of `data[1]`.
However, the `data[4] == 0` assertion is expected to pass -- we should not havoc
the entire `data` array, if only a constant index if being modified.
|
