Frama-C When using Frama-C in a series of benchmarks or test suites, especially when they consist of several small programs, consider using -no-autoload-plugins for better performance. This post explains why it is useful, as well as its downsides. Minimize startup time with -no-autoload-plugins By default, running frama-c makes it load all...
Read MoreIn the previous post, we mentioned the official Frama-C Docker images. In this post, we present two examples where these images allow us to incorporate Frama-C in a continuous integration process: a Frama-C Github Action, as well as integration of Frama-C in a Gitlab CI pipeline. Github Action: run Frama-C/Eva...
Read MoreFrama-C now has official Docker images in the Docker Hub! In this post we describe what they contain and how we intend to evolve them. If you have other uses for Docker images, don’t hesitate to contact us! Official Frama-C Docker Images in Docker Hub Official Frama-C Docker images are...
Read MoreThe analysis scripts provided with Frama-C, which have been mentioned in this blog several times, are now documented in the Frama-C User Manual. This should provide a more complete and up-to-date experience concerning these scripts. Faster iterations with daily Frama-C snapshots Deploying analysis scripts usually required very long iteration times:...
Read MoreFrama-C has a somewhat obscure plug-in called Obfuscator, whose original purpose was to help industrial users give the Frama-C developers enough information about confidential use cases, for debugging and optimizations. However, sharing proprietary code is never easy: is the obfuscation good enough? Are there legal issues involved? Is it worth...
Read More