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

  • Subject: [Frama-c-discuss] another question about ptest.byte
  • From: stephane.duprat at (DUPRAT Stephane)
  • Date: Mon, 19 Dec 2011 10:30:42 +0000


I have another question about ptest.byte and a remark.

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 ?

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.

Thanks in advance,


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.