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] how jessie and why platform work to generate a .v output?
- Subject: [Frama-c-discuss] how jessie and why platform work to generate a .v output?
- From: x_cui at hotmail.com (Xiao-lei Cui)
- Date: Thu, 7 Nov 2013 20:47:27 -0500
- In-reply-to: <527BC6AE.4080002@inria.fr>
- References: <BAY169-W79E32D31379140AFC7E32B97F40@phx.gbl>, , , <5278F337.1000304@inria.fr>, , <BAY169-W128CAD85298D41CCD65B64A97F10@phx.gbl>, , <52790508.6090107@inria.fr>, <BAY169-W1275B332FFA0B46CAF8C29C97F00@phx.gbl>, <527BC6AE.4080002@inria.fr>
Hi Claude, Thanks for the tips! The work-around solves the problem. I will start playing with WHY3, and working on the ACSL specifications. cheers, xiaolei > Date: Thu, 7 Nov 2013 17:58:22 +0100 > From: Claude.Marche at inria.fr > To: frama-c-discuss at lists.gforge.inria.fr > Subject: Re: [Frama-c-discuss] how jessie and why platform work to generate a .v output? > > > Hi, > > In that case there is nothing wrong with your installation, but you hit > a subtile bug of Jessie in presence of an assert just before a return > statement. > > A simple, although strange I admit, work-around is to add an extra empty > statement ";" after the assert : > > > /*@ assert zz>0; @*/ ; > return y; > > - Claude > > -- > Claude March? | tel: +33 1 72 92 59 69 > INRIA Saclay - ?le-de-France | > Universit? Paris-sud, Bat. 650 | http://www.lri.fr/~marche/ > F-91405 ORSAY Cedex | > > > _______________________________________________ > 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/20131107/44496be1/attachment.html>
- References:
- [Frama-c-discuss] how jessie and why platform work to generate a .v output?
- From: x_cui at hotmail.com (Xiao-lei Cui)
- [Frama-c-discuss] how jessie and why platform work to generate a .v output?
- From: Claude.Marche at inria.fr (Claude Marché)
- [Frama-c-discuss] how jessie and why platform work to generate a .v output?
- From: x_cui at hotmail.com (Xiao-lei Cui)
- [Frama-c-discuss] how jessie and why platform work to generate a .v output?
- From: Claude.Marche at inria.fr (Claude Marché)
- [Frama-c-discuss] how jessie and why platform work to generate a .v output?
- From: x_cui at hotmail.com (Xiao-lei Cui)
- [Frama-c-discuss] how jessie and why platform work to generate a .v output?
- From: Claude.Marche at inria.fr (Claude Marché)
- [Frama-c-discuss] how jessie and why platform work to generate a .v output?
- Prev by Date: [Frama-c-discuss] RE : Problem on Plugin development with WP plugin
- Next by Date: [Frama-c-discuss] adding new provers to why3
- Previous by thread: [Frama-c-discuss] how jessie and why platform work to generate a .v output?
- Next by thread: [Frama-c-discuss] Frama-c - wp on Windows/Cygwin
- Index(es):