Generating code complexity metrics | HP UX Web Development Tools

◦Number of if statements

◦Number of return statements

◦Number of loop nests

◦Nesting level of each loop nest

◦Number of indirect calls

◦Number of direct calls

◦Targets of direct calls

◦Cyclomatic complexity

◦Cyclomatic complexity without switch

◦Cyclomatic complexity without exception handling

◦Cyclomatic complexity without switch and exception handling

◦Number of Thread Local Storage (TLS) variables

◦Number of mutexes

◦Number of lock calls

◦Number of unlock calls

For each indirect call site, cadvise emits the list of possible call targets.

•Cyclomatic Complexity

Cyclomatic complexity metric, developed by Thomas McCabe in 1976 ,measures the number of linearly-independent paths through a program module. It is an indicator for understandability and testability of a module. A lower value indicates more understandable and testable code. The +metrics option emits cyclomatic complexity by default.

•Indirect Call Targets

This refers to the list of functions that can be called at an indirect call site. Calculation of this metric leads to an increase in analysis time and so the +metrics option does not emit Indirect Call Targets by default. You need to specify ict as a suboption to the +metrics option for emission of indirect call targets. This causes emission of Indirect Call Targets in addition to all other default metrics.

The following example shows the code complexity metrics.

2.7 Generating code complexity metrics 15

Image 15

HP UX Web Development Tools manual Generating code complexity metrics

Contents

HP Code Advisor C.02.20 User Guide Page Contents Contents Related information Document conventions and symbolsAbout this document Intended audience Cadvise-help@lists.hp.com HP encourages your comments Cadvise user interface FeaturesCadvise user interface Features Introduction $ cadvise cc -c hello.c Advanced static code analysis $ cadvise -pdb ./mypdb +wlint aCC hello.cpp Supported compilers Getting started Using CadviseSteps in using cadvise Supported platforms Installing Cadvise Invoking Cadvise Integrating Cadvise with the makefiles and build process Using Cadvise as a wrapper around Compiler or LinkerFor information on PDB, see Using the Program Database PDB See the following makefile content Enabling different categories of diagnostic messages Generating code complexity metricsExample 2 Sample wrapper script Objfile.metrics Example 3 Generating code complexity metrics Generating code complexity metrics $ cat /tmp/example.c Example 4 Code complexity metrics +wcodeguide=rules-library Example 5 Writing a rule to enforce naming convention Source structure in the rules library Using the Program Database PDB Disabling locks in PDB operations PDB options tableSpecifying the PDB location Deleting PDB Example 9 Creating a PDB snapshot Creating a PDB snapshot at a specified locationDisplaying PDB version Example 8 Removing object file information from the PDB Using cross-file analysis UsageCross-file analysis options Crossfile=auto Example 15 Specifying the location of object files Enabling warnings selectively Configuring diagnostic messagesDiagnostic configuration options table Suppressing warnings selectively Interpreting selective warnings as errors Disabling warnings in a macroManaging warnings in a source file Cadvise report report-options logfile Generating reportsReport generation options table Cadvise report report-options -pdb pdbdir $cadvise report -summary -pdb testpdb -noheader Generating summary reportsGenerating file summary report Generating detailed report $ cadvise report -pdb testpdb -all To save reports, run the following commandGenerating Html report Example 23 Generating detailed report Example 24 Generating an XML report Printing diagnostics with specific diagnostic numbersFollowing example shows the command to generate XML report Generating XML report Example 26 Generating reports based on severity Suppressing diagnostics for specific filesGenerating reports based on severity $ cadvise report -pdb testpdb -diag $ cadvise report -pdb test.pdb -summary -include inflate.c Reporting diagnostics from specific filesReporting program complexity metrics $ cadvise report -pdb test.pdb -summary -exclude inflate.c Generating report for a module Example 29 Reporting program complexity metrics$ cadvise report -pdb gzip.pdb +metrics -include inflate.c $ cadvise report -pdb test.pdb -summary -module test1 Modifying the default severity level of a diagnosticSuppressing report header Generating PDB comparison report $ cadvise report -pdb tmp.pdb -basepdb tmp1.pdb -all Example 34 Generating detailed diff report with the header $ cadvise report -pdb tmp.pdb -basepdb tmp1.pdb -diag Example 35 Generating diff report for any particular warning $ cadvise -pdb pdb1 cc one.c two.c $ cadvise report -pdb tmp.pdb -basepdb tmp1.pdb -severity $ cadvise report -pdb new.pdb -basepdb old.pdb -all Report options file Example 41 Report options file Example 42 Generating a report using -migration optionGenerate report for migration related warnings Generating consolidated report from multiple PDBs $ cadvise report -pdb 1.pdb2.pdb3.pdb4.pdb -all Recommended process for analyzing the diagnostic messagesGenerating PDB diffs with multiple PDBs Report options interoperability $ cadvise report -pdb test.pdb -summary -include a.cb.c Example 44 Reporting options interoperability$ cadvise report -pdb test.pdb -diag 2549 -exclude b.c Example 45 Ignoring the -includeoption Example 47 Displaying the list of cadvise options Example 48 Using -noabortMiscellaneous driver options Help-h-H Following example shows the usage of -nobuildoption Example 49 Using -nobuild optionFollowing command creates the file cadvdir/foo.cad Example 51 Using -tee option Line generates the following messages Example 52 Using +opts filename option Categories of diagnostics with examples Categories of diagnostics tableDetecting generic programming errors Categories of diagnostics with examples Such cases, cadvise generates the following warning Example 53 Null pointer dereference check Such cases, cadvise generates the following warnings Example 54 Potential memory leak check Example 56 Out of scope access Example 55 Out of bound access Such cases, cadvise generates the following error Example 57 Use of pointer after freeExample 58 Allocator/deallocator mismatch Example 59 Signed bit field of length Detecting 32-bit to 64-bit migraton issuesDetecting endianness migration issues Example 60 Detecting 32-bit to 64-bit migraton issues Detecting potential security vulnerabilities Example 61 Detecting endian dependent code fragmentsConsider the following code fragment This case, cadvise generates the following error Detecting multi-threaded programming issues Example 63 Detecting multi-threaded programming issues Running cadvise generates the following errorDetecting potential performance improvement opportunities Detecting potential performance improvement opportunities Fixing the warnings by source change AC++ standard conformance and compatibility changes Incompatibilities on PA-RISC based systems Index Symbols