HP UX Web Development Tools manual PDB options table, Specifying the PDB location, Deleting PDB

Page 20

3.1 PDB options table

The following options help you manage the PDB:

“-pdb location” (page 20)

“-pdb_destroy” (page 20)

“-pdb_no_locking” (page 20)

“-remove” (page 20)

“-snapshot location” (page 21) “-pdb_version” (page 21)

Enables you to specify the location (path) of the PDB.

Removes the PDB specified with the –pdb option.

Allows you to not to use locks in PDB operations.

Removes information related to the specified object files from the PDB.

Creates a snapshot of the PDB at the specified location (path). Prints the PDB version and checks for compatibility.

3.2 Specifying the PDB location

The path specified may be relative or absolute, but you must ensure that the whole application build creates only one PDB. If the build of your application is done across multiple machines, you must ensure that the path specified is accessible from all the machines involved in creating the build.

Following is the syntax for changing the location of the PDB:

$cadvise <location> -pdb <pdbname>

Following is an example to specify the location of the PDB:

Example 6 Specifying the PDB Location

$cadvise -pdb testpdb /opt/aCC/bin/aCC 1.c

Where: testpdb is the location of the PDB.

3.3 Deleting PDB

This option enables you to delete the PDB when it is no longer required.

Following is the syntax for deleting PDB:

$cadvise -pdb_destroy -pdb <pdbname>

Following is an example to delete the PDB:

Example 7 Destroying PDB

$cadvise -pdb_destroy -pdb testpdb

Where: testpdb is the location of the pdb, to be deleted.

3.4 Disabling locks in PDB operations

The -pdb_no_lockingoption ensures that cadvise does not use locks in PDB operations. Cadvise uses locks implemented with lockf during some PDB operations, by default. If the user machine does not use lockd, or if there are any name resolution issues between the PDB host and client machines, the lockf calls do not execute for an indefinite period of time. Use the -pdb_no_lockingoption to workaround lockf related-issues in user systems. Locks are important if the user has to run cadvise analysis and reports simultaneously. If you do not use locks and run cadvise analysis in parallel with the reports, then there is a potential for incomplete or truncated reports. See also : manpages on lockf(2); lockd(1M).

3.5 Removing object file information from the PDB

The -removeoption removes from the PDB, any information such as logs, internal representation, and metrics related to the specified object files.

20 Using the Program Database (PDB)

Page 19 Page 21
Image 20
Page 19 Page 21
Contents HP Code Advisor C.02.20 User Guide Page Contents Contents Document conventions and symbols About this documentIntended audience Related informationHP encourages your comments Cadvise-help@lists.hp.comFeatures Cadvise user interface FeaturesIntroduction Cadvise user interfaceAdvanced static code analysis $ cadvise cc -c hello.cSupported compilers $ cadvise -pdb ./mypdb +wlint aCC hello.cppUsing Cadvise Steps in using cadviseSupported platforms Installing Cadvise Getting startedInvoking 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 processExample 2 Sample wrapper script Enabling different categories of diagnostic messagesGenerating code complexity metrics Example 3 Generating code complexity metrics Objfile.metricsGenerating 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 conventionUsing the Program Database PDB PDB options table Specifying the PDB locationDeleting PDB Disabling locks in PDB operationsCreating a PDB snapshot at a specified location Displaying PDB versionExample 8 Removing object file information from the PDB Example 9 Creating a PDB snapshotCross-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 selectivelyManaging 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 logfileGenerating summary reports Generating file summary reportGenerating detailed report $cadvise report -summary -pdb testpdb -noheaderTo save reports, run the following command Generating Html reportExample 23 Generating detailed report $ cadvise report -pdb testpdb -allPrinting diagnostics with specific diagnostic numbers Following example shows the command to generate XML reportGenerating XML report Example 24 Generating an XML reportSuppressing diagnostics for specific files Generating reports based on severity$ cadvise report -pdb testpdb -diag Example 26 Generating reports based on severityReporting 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 test1Example 34 Generating detailed diff report with the header $ cadvise report -pdb tmp.pdb -basepdb tmp1.pdb -allExample 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.cReport options file $ cadvise report -pdb new.pdb -basepdb old.pdb -allExample 42 Generating a report using -migration option Generate report for migration related warningsGenerating consolidated report from multiple PDBs Example 41 Report options fileRecommended process for analyzing the diagnostic messages Generating PDB diffs with multiple PDBsReport options interoperability $ cadvise report -pdb 1.pdb2.pdb3.pdb4.pdb -allExample 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.cExample 48 Using -noabort Miscellaneous driver optionsHelp-h-H Example 47 Displaying the list of cadvise optionsExample 49 Using -nobuild option Following command creates the file cadvdir/foo.cadExample 51 Using -tee option Following example shows the usage of -nobuildoptionExample 52 Using +opts filename option Line generates the following messagesDetecting 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 warningExample 54 Potential memory leak check Such cases, cadvise generates the following warningsExample 55 Out of bound access Example 56 Out of scope accessExample 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 lengthConsider 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 errorDetecting 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 changesSymbols Index
Top Page Image Contents