HP Code Advisor

3.1 PDB Options Table
The following options help you manage the PDB:
Enables you to specify the location (path) of the PDB.-pdb location
Removes the PDB specified with the –pdb option.-pdb_destroy
Do not use locks in PDB operations.-pdb_no_locking
Removes from the PDB any information related to the specified object
files.
-remove
Creates a snapshot of the PDB at the specified location (path).-snapshot location
Prints the PDB version and checks for compatibility-pdb_version
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 performing 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 3-1 Specifying the PDB Location
$cadvise /opt/aCC/bin/aCC 1.c -pdb testpdb
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 needed.
Following is the syntax for deleting PDB:
$cadvise -pdb_destroy -pdb <pdbname>
Following is an example to destroy the PDB:
Example 3-2 Destroying PDB
$cadvise -pdb_destroy -pdb testpdb
Where: testpdb is the location of the pdb, to be destroyed.
3.4 Disabling locks in PDB operations
The -pdb_no_locking option 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_locking option 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).
26 Using the Program Database (PDB)