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] How to use the frama-c builtins programmatically?

  • Subject: [Frama-c-discuss] How to use the frama-c builtins programmatically?
  • From: abiao.yang at gmail.com (David)
  • Date: Mon, 02 Sep 2013 20:00:25 +0800
  • In-reply-to: <mailman.4956.1378112165.1217.frama-c-discuss@lists.gforge.inria.fr>
  • References: <mailman.4956.1378112165.1217.frama-c-discuss@lists.gforge.inria.fr>
? 2013/9/2 16:56, frama-c-discuss-request at lists.gforge.inria.fr ??:
> I think there is some misunderstanding here. When you add
> /usr/local/share/frama-c/libc/fc_runtime.c to the list of source files
> to consider, all C implementations present in this file will be
> treated as C functions to be analyzed, exactly that the functions that
> are defined in file.c Value analysis built-in mechanism allows to
> replace the normal analysis of a C function by a call to an OCaml
> function which operates directly to the internal states of Value
> analysis, simulating the behavior of the corresponding C function.
> These two behaviors are completely different. What are you trying to
> achieve?
Dear Virgile,

Thank you for replying me promptly.
I am trying to treat those C functions in fc_runtime.c to be analyzed.
I can ahieve this by codeing like this:

Kernel.Files.add "/usr/local/share/frama-c/libc/fc_runtime.c";

Thanks again.

David