Frama-C-discuss mailing list archives
This page gathers the archives of the old Frama-C-discuss archives, that was hosted by Inria's gforge before its demise at the end of 2020. To search for mails newer than September 2020, please visit the page of the new mailing list on Renater.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Frama-c-discuss] Frama-C: Detecting unreachable code?
- Subject: [Frama-c-discuss] Frama-C: Detecting unreachable code?
- From: mohamed.iguernelala at ocamlpro.com (Mohamed Iguernelala)
- Date: Fri, 24 Jan 2014 14:08:45 +0100
- In-reply-to: <B517F47C2F6D914AA8121201F9EBEE6701C7660449A8@Mail1.FCMD.local>
- References: <B517F47C2F6D914AA8121201F9EBEE6701C7660449A7@Mail1.FCMD.local> <52E0C26F.2000605@linux-france.org> <20140123082550.GA7256@opentech.at> <CAOH62JhyfqOmKmw5iKjx1CSifK2X6ajxZBxd--h4_nK-3OxmrA@mail.gmail.com> <52E0D85C.3060504@cea.fr>, <CAOH62Jj=TOozP8yxRV7-ECSUknpVhe6_eeMwPuQGOJTYJD+5fg@mail.gmail.com> <B517F47C2F6D914AA8121201F9EBEE6701C7660449A8@Mail1.FCMD.local>
Hi, Actually, the verification condition generated for Alt-Ergo is of the form: *... (* Context: first-order axioms for memory model, .... *) ... goal g: false* Obviously, the VC is invalid if you condiser that the context is consistent. But in general, SMT solvers answer "unknown" instead of "invalid" when working on fragments of logic on which they are not complete. I tried other provers: cvc3 says "unknown", and cvc4 and z3 timeout after 10 seconds. Mohamed Iguernelala. Senior R&D Engineer, OCamlPro Research Associate, VALS team, LRI. http://www.iguer.info Le 24/01/2014 03:36, Dharmalingam Ganesan a ?crit : > Hi, > > Thanks for all responses. I'm not sure why the following code cannot considered invalid; I always get "unknown". > > Any comments? > > frama-c -wp -wp-rte non_sense.c -lib-entry > > > > int i = 0; > > /*@ > @ behavior BUG: > @ assumes i == 5; > @ ensures \result == -2; > */ > > int main() > { > if (0 <= i && i <= 10) > { > return -1; > } > > if (i == 5) > { > return -2; > } > > return 0; > } > > _______________________________________________ > Frama-c-discuss mailing list > Frama-c-discuss at lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/frama-c-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gforge.inria.fr/pipermail/frama-c-discuss/attachments/20140124/32f4695c/attachment.html>
- References:
- [Frama-c-discuss] Frama-C: Detecting unreachable code?
- From: dganesan at fc-md.umd.edu (Dharmalingam Ganesan)
- [Frama-c-discuss] Frama-C: Detecting unreachable code?
- From: dmentre at linux-france.org (David MENTRE)
- [Frama-c-discuss] Frama-C: Detecting unreachable code?
- From: der.herr at hofr.at (Nicholas Mc Guire)
- [Frama-c-discuss] Frama-C: Detecting unreachable code?
- From: pascal.cuoq at gmail.com (Pascal Cuoq)
- [Frama-c-discuss] Frama-C: Detecting unreachable code?
- From: nicky.williams at cea.fr (Nicky Williams)
- [Frama-c-discuss] Frama-C: Detecting unreachable code?
- From: pascal.cuoq at gmail.com (Pascal Cuoq)
- [Frama-c-discuss] Frama-C: Detecting unreachable code?
- From: dganesan at fc-md.umd.edu (Dharmalingam Ganesan)
- [Frama-c-discuss] Frama-C: Detecting unreachable code?
- Prev by Date: [Frama-c-discuss] Frama-C: Detecting unreachable code?
- Next by Date: [Frama-c-discuss] Frama-C: Detecting unreachable code?
- Previous by thread: [Frama-c-discuss] Frama-C: Detecting unreachable code?
- Next by thread: [Frama-c-discuss] Frama-C: Detecting unreachable code?
- Index(es):