Task: See How Results Have Changed After Upgrading CodeSonar

• Preliminaries
• Method
• Links

This task will use the following for brevity.

• interface:hubport is your hub location.
• hubdir is your hub directory.
• projname is the name of the project you are analyzing.
• Examples are based on a project built with make. Substitute your own build command and full rebuild mechanism as appropriate.

Preliminaries

This task requires that you have analyzed the project before upgrading. Work through the following steps before upgrading CodeSonar.

1. Start the hub, if it is not already running.
   codesonar hub-start hubdir interface:hubport
2. In order to see how the analysis results have changed, you will need analysis results for the latest version of projname. If you do not already have such results, perform a CodeSonar build/analysis of projname and send the results to your hub. For example:
   codesonar analyze projname interface:port make
3. If you are currently signed in to the hub, sign out.

Method

Once you have a hub with baseline results and are ready to upgrade, proceed as follows.

1. Shut down the hub.
   codesonar hub-stop interface:hubport
   (You may be prompted for hub user account credentials.)
2. Upgrade CodeSonar on the hub machine.
   • See the Installation section for full details.
   • You may also need to refresh the CodeSonar license.
   • If you are not installing the new version of CodeSonar in the same place you stored the old version, make sure you update your PATH environment variable.
3. Upgrade CodeSonar on the machine you use to run the build/analysis, if this is different to the hub machine.
4. On the hub machine, verify that your PATH setting is enabling your system to find the new version of CodeSonar.
   which codesonar
5. On the hub machine, start the hub.
   codesonar hub-start hubdir interface:hubport
   As part of the hub starting process, CodeSonar will upgrade the hub database to work properly with the new version of CodeSonar. Depending on the size of the database, this may take several minutes.
6. On the build/analysis machine, verify that your PATH setting is enabling your system to find the new version of CodeSonar.
   which codesonar
7. Perform a CodeSonar build/analysis based on a full rebuild of projname. For example:
   make clean
   codesonar analyze projname interface:port make
8. Open the web GUI and list the analyses for projname.
9. Click the Analysis table heading to show a table menu, then select Show > Analysis ID to add the Analysis ID column to the table.

   

10. The most recent analysis is the one you performed with the new version of CodeSonar. Note its analysis ID. Call this new_id.
11. The next-most-recent analysis is your baseline analysis. Note its analysis ID. Call this old_id.
12. Construct the search string:
    aid=new_id DIFFERENCE aid=old_id
13. Paste the search string into the search field, select warnings in all projects from the search domain/scope menu, and click Search.

    A search results page will open.

14. Select all from the Visible Warnings menu.

    The search results page now displays all the representative instances of warnings found in the new analysis but not the baseline analysis.

15. If you want to be able to access this search from the Visible Warnings menu in future, save it as a named search.
16. Conversely, to see the representative instances of warnings found in the baseline analysis but not the new analysis:
    1. Construct the search string:
       aid=old_id DIFFERENCE aid=new_id
    2. Paste the search string into the search field, select warnings in all projects from the domain/scope menu, and click Search.
    3. Select all from the Visible Warnings menu.

Links

Related tasks

• Sort a warning table
• Show full file paths in a warning table
• Refine a search
• Save a named search
• Show all warnings on the hub
• View a warning report

Using CodeSonar

• Typical CodeSonar Tasks
• CodeSonar GUI Reference