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] French slides to present Frama-C, value analysis and Jessie

  • Subject: [Frama-c-discuss] French slides to present Frama-C, value analysis and Jessie
  • From: hollas at (Boris Hollas)
  • Date: Tue, 01 Feb 2011 11:55:09 +0100
  • In-reply-to: <>
  • References: <> <> <>

On Tue, 2011-02-01 at 09:38 +0100, David MENTRE wrote:
> loops (and "all programs are loops", quoting a participant). I talked
> about the skein analysis in Value analysis tutorial which is able to
> provide some interesting result and the use of -slevel. But I lack
> first hand practice on applying value analysis to large code. Is it a
> real issue on control code, for example?

Control code contains very few loops. Often, there's an outer
while(true) loops to repeatedly execute control statements (similar to
while programs in Kleene normal form).

> Regarding Jessie: "annotations have the same size as code!" and "what
> about error in annotations?". For the former remark, I could only tell

Yes, some less bright programmers write annotations that are trivially
true and hence verify. Unfortunately, the programmers who write the most
buggy code also have the least knowledge in formal logic, which is
required to write reasonable annotations.

> One of the attendee followed a lesson on code proof using a functional
> approach and PVS powerful tactics made by a researcher at INRIA Rennes
> (Thomas Genet) and told the approach was more powerful and simple. I
> answered that the discussion between the two approaches is still
> on-going. :-)

Do you know more about this approach?