1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
|
CORE dfcc-only
main.c
--no-malloc-may-fail --dfcc main --apply-loop-contracts
^EXIT=10$
^SIGNAL=0$
^\[main.loop_assigns.\d+\] line 11 Check assigns clause inclusion for loop .*: SUCCESS$
^\[main.loop_invariant_base.\d+\] line 11 Check invariant before entry for loop .*: SUCCESS$
^\[main.loop_invariant_step.\d+\] line 11 Check invariant after step for loop .*: SUCCESS$
^\[main.loop_step_unwinding.\d+\] line 11 Check step was unwound for loop .*: SUCCESS$
^\[main.assigns.\d+\] .* Check that i is assignable: SUCCESS$
^\[main.assigns.\d+\] .* Check that data\[(\(signed (long (long )?)?int\))?i\] is assignable: SUCCESS$
^\[main\.assertion\.\d+\] .* assertion data\[5\] == 0: FAILURE$
^\[main\.assertion\.\d+\] .* assertion data\[5\] == 1: FAILURE$
^VERIFICATION FAILED$
--
--
Test case related to issue #6020: it checks that dynamically allocated arrays
are correctly havoced when enforcing loop invariant contracts.
The `data[5] == 0` assertion is expected to fail since `data` is havoced.
The `data[5] == 1` assertion is also expected to fail since the invariant does
not reestablish the value for `data[5]`.
|
