Fixing the warnings by source change | HP UX Web Development Tools

9 Fixing the warnings by source change

The HP Code Advisor Diagnostics Reference Guide document enables you fix the warnings with a brief description for a partial list of diagnostics emitted by cadvise. In this document, there are four sections for each description as mentioned below:

•The Cause section

Discusses the possible reasons for the diagnostic to be emitted.

•The Example section

Provides relevant sample code segments that result in the specific diagnostic. The sample code segments are not complete, compilable programs - you might have to include the necessary header files, provide the code segment within main() function (if one is not provided in the code segment) and use necessary compiler options (such as +w, +wlint) to reproduce the diagnostic.

•The Action section

Suggests possible solutions to avoid the diagnostic.

•The Reference section

Consists of relevant section numbers from the standard document if the diagnostic pertains to any language standard.

For more information, see HP Code Advisor Diagnostics Reference Guide at the website:

http://www.hp.com/go/cadvise.

56 Fixing the warnings by source change

Image 56

HP UX Web Development Tools manual Fixing the warnings by source change

Contents

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