Cycle Detection

Identify Cyclical Dependencies at Different Levels With Static Code Analysis

Call cycles during runtime are hazardous. Functions call each other and therefore pose the risk of endless recursion. If a direct cycle occurs, there is a risk the system can crash at any time. While short cycles may be recognized and resolved – even by the developers – during a review, it is virtually impossible a human observer to detect longer cycles when reviewing manually. Axivion Static Code Analysis helps you reliably verify freedom from cycles.

Cycle Detection 2 (2)

Protect Your Code From Recursions, Component Cycles and Include Cycles

The analysis recognizes cyclical dependencies on different levels. It can identify and monitor not only call cycles (recursions), but also component cycles and include cycles.

Include files often use each other. This produces mutual dependencies between the files and the resulting build problems. In addition, it hinders the developer in understanding the code.

Detecting these kind of cycles too late in the development process, often means there is no simple way to resolve them as the cycle has become part of the intended functionality. Continuous verification prevents this from happening. As these are merely a loop in the call hierarchy for Axivion Statc Code Analysis, they can be easily identified.

Contact Us

Contact Us

Download the Brochure


Dead Code Analysis

Read More

Defect Analysis

Read More