Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • F frama-c
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 168
    • Issues 168
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • pub
  • frama-c
  • Issues
  • #2070
Closed
Open
Issue created Oct 17, 2011 by mantis-gitlab-migration@mantis-gitlab-migration

Frama-C should return a non-null return value when a goal could not be validated

ID0000987: This issue was created automatically from Mantis Issue 987. Further discussion may take place here.


Id Project Category View Due Date Updated
ID0000987 Frama-C Kernel public 2011-10-17 2012-02-15
Reporter sylvain nahas Assigned To signoles Resolution no change required
Priority normal Severity feature Reproducibility always
Platform - OS - OS Version -
Product Version Frama-C Nitrogen-20111001 Target Version - Fixed in Version -

Description :

Feature description:

Currently Frama-C returns a value of 0 to the OS whatever are the status of the proof obligations. It should provide a command line switch that makes him return a non-null value in this case. The default behavior would stay the same.

Use-Case:

QA purposes.

The need arise when automatizing source code validation with Makefiles. Makefile will stop execution when a building command returns a value different of 0, but this does not function with Frama-C, even if one may wish to stop the build when the source is not completely validated. In the last case a completed build run means 100% validated code with respect to annotations.

This would be useful as well when writing hooks script on VCS servers (think subversion).

Note: the option may provide several levels.

Attachments

  • werror.tar.gz
  • werror-2.tar.gz
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking