Procedure

• Properties
• Accessing Procedure Information
• Availability

Properties

CodeSonar stores the following information about each procedure.

Accessing Procedure Information

Procedure information is available in the CodeSonar GUI as follows.

Availability

When a source file is analyzed, file properties are submitted to the hub and stored with the rest of the analysis information. For space reasons, the file listing is not submitted to the hub, but is instead stored in the project analysis directory ( pfilesname.prj_files/). For full details, see Source Files: Availability.

Procedure properties for the procedures defined in the source file are also stored in the project analysis directory, again for space reasons. The analysis will remove any procedure information previously stored in the project analysis directory before storing the new information.

The project analysis directory is thus the only location storing any information about an analyzed procedure: neither the procedure listing nor the procedure properties are recorded on the hub.

• For local-managed analyses, the CodeSonar build directory and analysis directory are the same directory.
  If there are multiple analyses of the same project with the same build directory, the build directory and thus the analysis directory are reused.
• For remote-managed analyses, the CodeSonar build directory is copied to a separate analysis directory at the beginning of the analysis phase.
  There can be multiple analyses of the same build directory, but the analysis directory for each of these analyses will be distinct. In particular, the parent directory for each analysis directory is named with the analysis ID.

When an analysis A is local-managed, its build directory and analysis directory are the same directory. If there is a subsequent analysis B with the same build/analysis directory, the previous files will be overwritten and the hub will only be able to interact with procedure information for analysis B.

When an analysis A is remote-managed, its analysis directory is always unique and cannot be affected by future analyses. When such an analysis transitions to daemon mode, the hub will be able to interact with the procedure information for analysis A even if there have been subsequent analyses of the same project.
If you want to take advantage of this behavior, specify the -remote or -remote-archive option in your build/analysis command.

The remainder of this page details various scenarios for local-managed analysis information.

Procedure Information Availability for Local-Managed Analyses

The remainder of this page details various scenarios for local-managed analysis information.
These scenarios are not applicable for remote-managed analyses (including those that are remote-managed only after transition to daemon mode), because each remote-managed analysis has its own distinct analysis directory and so its files are always available unless the analysis is deleted from the hub.

• If you do not branch any analysis, remove any analysis from the hub, or restore any project analysis directory from backup, each project analysis directory contains the procedure properties and source files from the most recent analysis of the project.

  

  • Procedure properties displayed in Procedure Search Results, Metric Report, and the Analysis: Procedures tab are obtained from the project analysis directory by the analysis daemon. If you request procedure properties from an older analysis, CodeSonar will display a notification message with the resulting table of procedure information, indicating that the information is from the currently-stored analysis rather than the requested one.
  • Each entry in a table of procedure information is linked to a Source Listing, scrolled to the procedure definition. This listing is likewise obtained from the project analysis directory.
• To re-analyze a project without removing older versions of its procedure properties and source files, make a new analysis branch. Each analysis branch has its own project analysis directory, so the contents of other project analysis directories are not modified.

  

• If an analysis is removed from the hub, the web GUI will not provide any access to procedure information from that analysis. Deleting the analysis whose information is currently stored in the project analysis directory thus means that tables of procedures that would otherwise have presented information from that analysis will be empty.

  

• If a project analysis directory is restored from backup, procedure properties and listings will reflect the restored information.