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] RE : another question about ptest.byte

Hello,

Thanks to Pascal and Virgile,

DONTRUN and make ptests_local_config.cmo were helpful for me.

Non-reg testing are really facilitated by the ptest.byte tool.

Happy Holidays,

Stephane



De : frama-c-discuss-bounces at lists.gforge.inria.fr [mailto:frama-c-discuss-bounces at lists.gforge.inria.fr] De la part de PREVOSTO Virgile
Envoy? : lundi 19 d?cembre 2011 12:35
? : Frama-C public discussion
Objet : [Frama-c-discuss] RE : another question about ptest.byte

Just to complete what Pascal just said:

- You can add some comment in the  DONTRUN: line, e.g. to indicate the name of the master file that is supposed to trigger the test
- the configuration of ptests can be altered by a ptests_local_config.ml file: if ptests.byte is launched in a directory which contains
ptests_local_config.cmo, it will dynamically load this file. In particular, if you're including Frama-C's Makefile.plugin in your own
Makefile and have set the appropriate variables (namely PLUGIN_TESTS_DIRS, possibly PLUGIN_TESTS_LIBS),
make ptests_local_config.cmo should create an appropriate configuration.

Best regards,
--
E tutto per oggi, a la prossima volta
Virgile
________________________________
De : frama-c-discuss-bounces at lists.gforge.inria.fr [frama-c-discuss-bounces at lists.gforge.inria.fr] de la part de Pascal Cuoq [pascal.cuoq at gmail.com]
Date d'envoi : lundi 19 d?cembre 2011 11:47
? : Frama-C public discussion
Objet : Re: [Frama-c-discuss] another question about ptest.byte
Hello St?phane,
On Mon, Dec 19, 2011 at 11:30 AM, DUPRAT Stephane <stephane.duprat at atos.net<mailto:stephane.duprat at atos.net>> wrote:
The question is about tests with multiple files. In first use of ptest, a test is identified by a sourcefile. But is it possible to make a test with several files in the same Frama-C session ?

Yes. The directory tests/idct contains such a test: the files ieee_1180_1990.c and idct.c only make sense when analyzed together. In order to do this, idct.c contains:
/* run.config
   DONTRUN:
*/

and ieee_1180_1990.c contains:
/* run.config
   OPT: -float-normal -val -deps -out -input tests/idct/idct.c share/math.c -journal-disable -remove-redundant-alarms
*/

in which "tests/idct/idct.c" is the important part for you.

The remark is about a message error that I have when I launch ptest.byte without arguments:
>$ ptests.byte
>Fatal error: exception Sys_error("tests/idct: Not a directory")

In my configuration, I have a directory named tests in which I have a subdir for each familiy tests.
And for example, "ptests.byte test_XX" is working well.

People who use ptests outside of its normal context provide a different ptests_config.ml<http://ptests_config.ml> than the one generated by Frama-C's configure in ptests/.

Pascal


________________________________

Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant ?tre assur?e sur Internet, la responsabilit? du groupe Atos ne pourra ?tre engag?e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne saurait ?tre engag?e pour tout dommage r?sultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavors to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gforge.inria.fr/pipermail/frama-c-discuss/attachments/20111222/f0723a36/attachment.htm>