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: dmentre at linux-france.org (David MENTRÉ)
Date: Sun, 5 Feb 2017 19:13:48 +0100
In-reply-to: <8C62BC92-DCA3-4AEE-91FF-BB7612047141@fokus.fraunhofer.de>
References: <mailman.19.1486206007.28592.frama-c-discuss@lists.gforge.inria.fr> <8C62BC92-DCA3-4AEE-91FF-BB7612047141@fokus.fraunhofer.de>

Hello Jens,

Le 2017-02-05 Ã  09:38, Gerlach, Jens a Ã©crit :
> 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.

Have you tried the -save and -load options? Are there WP specific things
that are missing from the loaded session?

Best regards,
david

Follow-Ups:
- [Frama-c-discuss] Making frama-c-gui a read-only tool?
  - From: loic.correnson at cea.fr (Loïc Correnson)

References:
- [Frama-c-discuss] Making frama-c-gui a read-only tool?
  - From: jens.gerlach at fokus.fraunhofer.de (Gerlach, Jens)

Prev by Date: [Frama-c-discuss] Making frama-c-gui a read-only tool?
Next by Date: [Frama-c-discuss] Making frama-c-gui a read-only tool?
Previous by thread: [Frama-c-discuss] Making frama-c-gui a read-only tool?
Next by thread: [Frama-c-discuss] Making frama-c-gui a read-only tool?
Index(es):
- Date
- Thread