Contents | HP UX Web Development Tools specs

Contents
About this document		5
Intended audience		5
Document conventions and symbols		5
Related information		5
HP encourages your comments		6
1 Introduction		7
1.1 Cadvise user interface		7
1.2 Features		7
1.2.1 Advanced static code analysis		8
1.2.2 Defect detection		8
1.2.3 Security vulnerability checks		8
1.2.4 Porting and migration		8
1.2.5 Detection of pre-defined or user-defined coding guideline violation		8
1.2.6 Easy to integrate and use		8
1.2.7 Supported compilers		9
2 Using Cadvise		10
2.1 Getting started		10
2.1.1 Supported platforms		10
2.1.2 Installing Cadvise		10
2.2	Steps in using cadvise	10
2.3 Invoking Cadvise		11
2.4	Using Cadvise as a wrapper around Compiler or Linker	12
2.5 Integrating Cadvise with the makefiles and build process		12
2.6	Enabling different categories of diagnostic messages	13
2.7	Generating code complexity metrics	13
2.8	Detecting violation of pre-defined or user-defined coding guidelines	17
3 Using the Program Database (PDB)		19
3.1 PDB options table		20
3.2	Specifying the PDB location	20
3.3	Deleting PDB	20
3.4	Disabling locks in PDB operations	20
3.5 Removing object file information from the PDB		20
3.6	Creating a PDB snapshot at a specified location	21
3.7	Displaying PDB version	21
4 Using cross-file analysis		22
5 Configuring diagnostic messages		25
5.1 Diagnostic configuration options table		25
5.2	Suppressing warnings selectively	25
5.3	Enabling warnings selectively	25
5.4	Interpreting selective warnings as errors	26
5.5	Disabling warnings in a macro	26
5.6	Managing warnings in a source file	26
6 Generating reports		27
6.1 Report generation options table		27
6.2 Generating summary reports		28
6.3	Generating file summary report	28
6.4	Generating detailed report	28
6.5	Generating HTML report	29

Contents 3

Image 3

HP UX Web Development Tools manual Contents

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