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] Problems with Frama-C libc


On 18/01/2012 10:52, Pascal Cuoq wrote:
> The headers in `frama-c -print-path`/libc are, literally, untested.
> They should be assumed to contain syntax errors or unsatisfiable
> specifications until shown otherwise.

This is not entirely true. These headers are not used that often, and 
some of the functions are grossly under-specified, but at least it 
That said, these headers (as most advanced ACSL specification) are 
primarily intended for use with WP or Jessie. For Value Analysis, you 
might have better luck by adding on the command line the corresponding 
.c implementations. In particular, with the string.c implementation:
frama-c-gui -cpp-extra-args="-I`frama-c -print-path`/libc" -val file.c 
`frama-c -print-path`/libc/string.c

the call to printf is not seen as dead.

Best regards,
E tutto per oggi, a la prossima volta