#50 Improve Frama-C analysis
Opened 6 years ago by athoscr. Modified 6 years ago

Frama-C is a different analyzer: it does need to know the path to all C source code files and headers. We need to improve our heuristics on how to find those files and exit in a cleaner way when it does not find them.

See util/dockerfiles/frama-c/run-analysis.sh


Metadata Update from @davidcarlos:
- Issue tagged with: Enhancement

6 years ago

run-analysis.sh is the same as docker-entrypoint.sh? The given path on description don't match with any file named run-analysis

Yes, this file was renamed after we opened this issue! Thanks for noticing and reporting here :)

I have been playing with Frama-C analyses and I realized that it is very hard to have a generic path to run the analyses. I wonder if we could use white lists to run the analyses, where we add specific directives to analyze specific projects. When there are no entries in the whitelist for the project, we try the generic approach.

We can check the logs from time to time to find new projects to add to the white lists. Any thoughts?

Login to comment on this ticket.

Metadata