There is no report for the loop XXX from module XXX. It is due to one or several reasons among the following ones:
- the loop does not match with the filter described in the filter field of the configuration file;
- the loop has been excluded in the configuration file. Check if the loop has been added in the filter excluded_areas;
- no debug data are attached to this loop. Check if your application has been compiled with -g option or add --force-all-loops to analyze loops without debug data;
- the loop has more than 4 paths. This value can be changed using the field maximal_path_number in the configuration file.
- the loop has a coverage lower than the minimal threshold set by object_coverage_threshold
- the loop contains a call to a recursive function.
All analyzed loops are listed on the page
Loops