frama-c issues
https://git.frama-c.com/pub/frama-c/-/issues
2021-02-22T12:56:30Z
https://git.frama-c.com/pub/frama-c/-/issues/216
Strange dot callgraphs
2021-02-22T12:56:30Z
mantis-gitlab-migration
Strange dot callgraphs
ID0000989:
**This issue was created automatically from Mantis Issue 989. Further discussion may take place here.**
---
| **Id** | **Project** | **Category** | **View** | **Due Date** | **Updated** |
| --- | --- | --- | --- | --- | --- ...
ID0000989:
**This issue was created automatically from Mantis Issue 989. Further discussion may take place here.**
---
| **Id** | **Project** | **Category** | **View** | **Due Date** | **Updated** |
| --- | --- | --- | --- | --- | --- |
| ID0000989 | Frama-C | Plug-in > callgraph | public | 2011-10-19 | 2018-11-30 |
| | | | | | |
| --- | --- | --- | --- | --- | --- |
| **Reporter** | Anne | **Assigned To** | signoles | **Resolution** | fixed |
| **Priority** | normal | **Severity** | minor | **Reproducibility** | have not tried |
| **Platform** | - | **OS** | - | **OS Version** | - |
| **Product Version** | - | **Target Version** | - | **Fixed in Version** | Frama-C Oxygen-20120901 |
### Description :
First of all, the callgraph shown in the GUI is not the same than the one generated with the [-cg] option. In the GUI, some of the functions are not displayed at all (g1 and g2 in the enclosed example).
Moreover, in both graphs (from the GUI and the command line), there is an edge between [g] and [nxt] even if [g] doesn't directly call [nxt]...
## Attachments
- [toto.c](/uploads/32fad344b4c6d0d290edf568bdd94f1b/toto.c)
https://git.frama-c.com/pub/frama-c/-/issues/219
Too many edges in call graph
2021-02-22T12:56:35Z
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:
**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](/uploads/490d044b58af5d6a44bce73501b37139/scg-frama.ps)