-
Notifications
You must be signed in to change notification settings - Fork 274
SVCOMP-benchmark incorrect (valid-deref) #3427
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
The benchmark: https://github.com/sosy-lab/sv-benchmarks/blob/master/c/ldv-memsafety/memleaks_test3_false-valid-free.i results in: Violated property: VERIFICATION FAILED where 5.8 resulted in: Violated property: VERIFICATION FAILED |
The benchmark: https://github.com/sosy-lab/sv-benchmarks/blob/master/c/memsafety-ext3/freeAlloca_false-valid-free.c results in: Violated property: VERIFICATION FAILED I'm not sure what the previous result was. The correct result would be "FALSE(valid-free)". |
Closing as the benchmarks are no longer available and so cannot reproduce. Please reopen if you believe this is erroneous/with a link to an appropriate example. |
Reporting on one SVCOMP benchmarks that were working in previous versions (5.8) but CBMC give incorrect result now. The benchmark code is here:
https://github.com/sosy-lab/sv-benchmarks/blob/master/c/memsafety/test-0521_true-valid-memsafety.c
CBMC version: 5.10
Operating system: 64-bit linux
Exact command line resulting in the issue: ./cbmc --graphml-witness witness.graphml --32 --propertyfile ../sv-benchmarks/c/MemSafety.prp ../sv-benchmarks/c/memsafety/test-0521_true-valid-memsafety.i
What behaviour did you expect:
VERIFICATION SUCCESSFUL
EC=42
UNKNOWN
What happened instead:
Violated property:
file ../sv-benchmarks/c/memsafety/test-0521_true-valid-memsafety.i line 715 function main
dereference failure: dead object in *pdst
!(POINTER_OBJECT(pdst) == POINTER_OBJECT(__CPROVER_dead_object))
VERIFICATION FAILED
EC=10
FALSE(valid-deref)
The text was updated successfully, but these errors were encountered: