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] preprocessing a file for E-ACSL

Subject: [Frama-c-discuss] preprocessing a file for E-ACSL
From: jens.gerlach at fokus.fraunhofer.de (Gerlach, Jens)
Date: Mon, 24 Aug 2020 09:47:11 +0000
In-reply-to: <7cb1c47d-a08e-2b63-68a8-fc032473591b@cea.fr>
References: <C61029F3-2D2A-453F-BD71-9191F422FD76@fokus.fraunhofer.de> <7cb1c47d-a08e-2b63-68a8-fc032473591b@cea.fr>

Hello AndrÃ©,

thanks a lot for pointing out â€š-ocodeâ€˜ to me!

Jens

> Am 24.08.2020 um 11:41 schrieb Andre Maroneze <Andre.MARONEZE at cea.fr>:
> 
> Did you try using "-ocode find_main.i"? It's the usual option to save the normalized source code produced by Frama-C, without having other messages redirected to the file. "-print" tells Frama-C to print the output, and "-ocode" tells Frama-C where to print it (stdout, by default).
>

References:
- [Frama-c-discuss] preprocessing a file for E-ACSL
  - From: jens.gerlach at fokus.fraunhofer.de (Gerlach, Jens)
- [Frama-c-discuss] preprocessing a file for E-ACSL
  - From: Andre.MARONEZE at cea.fr (Andre Maroneze)

Prev by Date: [Frama-c-discuss] preprocessing a file for E-ACSL
Next by Date: [no subject]
Previous by thread: [Frama-c-discuss] preprocessing a file for E-ACSL
Next by thread: [no subject]
Index(es):
- Date
- Thread