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] Making frama-c-gui a read-only tool?

  • Subject: [Frama-c-discuss] Making frama-c-gui a read-only tool?
  • From: jens.gerlach at fokus.fraunhofer.de (Gerlach, Jens)
  • Date: Sun, 5 Feb 2017 08:38:25 +0000
  • In-reply-to: <mailman.19.1486206007.28592.frama-c-discuss@lists.gforge.inria.fr>
  • References: <mailman.19.1486206007.28592.frama-c-discuss@lists.gforge.inria.fr>
Hello,

With respect to Frama-C/WP I agree with André and David that I am using the GUI to inspect results.
Of course, I use the GUI also to experiment with the timeout or start the Coq IDE.

Since our ACSL examples build on each other we run WP on the command line when we have changed something.
If our scripts indicate that something is not verified anymore, then we start the GUI.
As of now this means that we have to rerun the analysis just to display the results of a previous run.
We therefore would like to have a dedicated “viewer mode” in the WP GUI just to display existing results.

Regards

Jens