Skip to content
GitLab
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 173
    • Issues 173
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • 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
  • #1889
Closed
Open
Issue created Nov 01, 2012 by Jochen Burghardt@burghardt

proc name in assigns clause causes crash

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


Id Project Category View Due Date Updated
ID0001293 Frama-C Plug-in > wp public 2012-11-01 2013-04-19
Reporter Jochen Assigned To correnson Resolution fixed
Priority normal Severity crash Reproducibility always
Platform - OS - OS Version -
Product Version Frama-C Oxygen-20120901 Target Version - Fixed in Version Frama-C Fluorine-20130401

Description :

Running "frama-c -wp ftest.c >ftest.log 2>&1" on the attached program, and yielding the attached log file, the Kernel reports an unexpected stack overflow. Although referring to a procedure name ("ftest") in an assigns-clause (line 4) is one of the most stupid user-errors that can be made, it should not cause a crash.

Attachments

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