Skip to content

GitLab

  • Menu
Projects Groups 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
    • Contributors
    • Graph
    • Compare
  • Issues 201
    • Issues 201
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • 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
  • #1259
Closed
Open
Created Mar 21, 2011 by David Delmas@ddelmas

wrong treatment for const arrays in lib-entry mode

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


Id Project Category View Due Date Updated
ID0000759 Frama-C Plug-in > Eva public 2011-03-21 2014-02-12
Reporter ddelmas Assigned To pascal Resolution fixed
Priority normal Severity major Reproducibility always
Platform - OS - OS Version -
Product Version Frama-C Carbon-20110201 Target Version Frama-C Oxygen-20120901 Fixed in Version Frama-C Oxygen-20120901

Description :

With the attache source file, frama-c fptr.c -lib-entry -main f -users

yields the below incorrect result: [users] ====== DISPLAYING USERS ====== f: h0 h1 ====== END OF USERS ==========

Attachments

  • fptr.c
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking