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
  • #1835

unexpected stack overflow in value analysis

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


Id Project Category View Due Date Updated
ID0001374 Frama-C Plug-in > Eva public 2013-02-25 2013-08-26
Reporter Jochen Assigned To yakobowski Resolution unable to reproduce
Priority normal Severity crash Reproducibility have not tried
Platform - OS - OS Version -
Product Version Frama-C Oxygen-20120901 Target Version - Fixed in Version -

Description :

Running 'frama-c -cpp-command "{{many cpp options}}" -no-unicode -pp-annot -slevel 300 -val-ignore-recursive-calls {{27 c files}}' caused an unexpected stack overflow after computing for about 18 hours and writing a 3.6 GB log file.

Unfortunately, I cannot provide the C sources; they were about 9400 lines (total), distributed to 27 C files.

I attach the backtrace log; it seemingly contains a loop starting at line 168 (bottommost repeated line in log file: 'Called from file "src/value/eval_funs.ml", line 86, characters 9-32').

Due to the long run-time it is also impossible to boil-down the code causing the stack overflow.

Attachments

  • backtrace.log
  • stackoverflow.ml
  • calledFuncs.txt
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking