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 209
    • Issues 209
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • pub
  • frama-c
  • Issues
  • #219

Closed
Open
Created Mar 28, 2010 by mantis-gitlab-migration@mantis-gitlab-migration

Too many edges in call graph

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


Id Project Category View Due Date Updated
ID0000435 Frama-C Plug-in > callgraph public 2010-03-28 2018-11-30
Reporter dclist Assigned To signoles 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 :

For some reason there are three edges on non-recursive function calls in the dot file produced by frama-c -scg (see attached)

frama-c -scg foo.dot foo.c && dot -Tpng foo.dot


int fact(int n) { if(n <= 0) return 0; else return fact(n-1); }

void foo(void) { printf("foo\n"); }

int main(void) { fact(10); foo(); }

Attachments

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