You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running the command cbmc test.c --function test_harness will infinitely repeat a line like Unwinding loop test.0 iteration 580 file test.c line 16 function test thread 0. I thought that this would go to the break statement but it appears that it does not. As when I comment out the while and break statement in the code above the assertion will hold that the variable i has changed from 0 to -1 and therefore that means that parse_end == s will be true for this code. Therefore, can you guys please help me understand why the break statement is not breaking the loop?
The text was updated successfully, but these errors were encountered:
The back-end assumes that each string is a singleton and, therefore,
taking the address of a particular string constant will always result in
the same value. The simplifier can use this information.
Fixes: diffblue#6966
It seems algebraic simplification did not consider the case of string constants when doing pointer comparison. Fixed in #6967. (Running this example with --unwind 2 --unwinding-assertions always produced the correct result.)
For the following code:
Running the command
cbmc test.c --function test_harness
will infinitely repeat a line likeUnwinding loop test.0 iteration 580 file test.c line 16 function test thread 0
. I thought that this would go to thebreak
statement but it appears that it does not. As when I comment out thewhile
andbreak
statement in the code above the assertion will hold that the variablei
has changed from0
to-1
and therefore that means thatparse_end == s
will be true for this code. Therefore, can you guys please help me understand why thebreak
statement is not breaking the loop?The text was updated successfully, but these errors were encountered: