bugGNU cflow - Bugs: bug #47110, Bug in recursion labelling


bug #47110: Bug in recursion labelling

Submitted by:  None
Submitted on:  Wed 10 Feb 2016 07:01:56 PM UTC  
Category:  None Severity:  3 - Normal
Item Group:  None Status:  None
Privacy:  Public Assigned to:  None
Open/Closed:  Open

Add a New Comment(Rich Markup)

You are not logged in

Please log in, so followups can be emailed to you.


Fri 12 Feb 2016 06:19:25 PM UTC, comment #1:

I've realized now that I should have sent this to the mailing list, and am about to do so.

Wed 10 Feb 2016 07:01:56 PM UTC, original submission:

I have the following two files:



The only difference is in the function bar, foo1 has return (*a).bar and foo2 has return a->bar. These are equivalent C statements. Running cflow on each, I get a different result:

cflow foo1.c
main() <int main () at foo1.c:11>:
bar() <int bar (struct foo a) at foo1.c:7> (R):
bar() <int bar (struct foo a) at foo1.c:7> (recursive: see 3)

cflow foo2.c
main() <int main () at foo2.c:11>:
bar() <int bar (struct foo a) at foo2.c:7>

When (*a).bar is used, cflow flags the use of bar as a recursive call even though it is not, and when a->bar is used cflow correctly determines that this is not a recursive call. This is using cflow 1.4.



(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


CC list is empty


Do you think this task is very important?
If so, you can add your encouragement to it.
This task has 0 encouragements so far.

Only logged-in users can vote.




No changes have been made to this item

Back to the top

Powered by Savane 3.3