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 171
    • Issues 171
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and 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
  • #2376
Closed
Open
Issue created Dec 15, 2009 by Jochen Burghardt@burghardt

"why" reports "unbound label"

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


Id Project Category View Due Date Updated
ID0000361 Frama-C Plug-in > jessie public 2009-12-15 2010-04-19
Reporter Jochen Assigned To cmarche Resolution fixed
Priority normal Severity minor Reproducibility always
Platform - OS - OS Version -
Product Version Frama-C Beryllium-20090901 Target Version - Fixed in Version Frama-C Boron-20100401

Description :

"why" reports an "unbound label" if a C-label of a statement having more than one effect (e.g. "b[j++] = 3;") is referred to in an "\at(...)" within an acsl-assertion. See attached file "labelBug.c"; process it with and without the initial "#define showBug" uncommented.

Attachments

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