Tips and tricks for the Klocwork Desktop plugin for CLion
| In this topic: |
Tips and tricks for the Klocwork Desktop plugin for CLion
The following includes information for configuring CLion for use with the Klocwork Desktop plugin.
Control what issues you see
Use 
to filter by status and owner.
To show only local issues, toggle Show local issues only
(relevant only for connected projects).
Group issues by 
file, 
severity or 
issue code.
Filter settings remain in effect for this project until you change them again, even if you close and reopen CLion.
Change project configuration settings
In the Settings > Tools > Klocwork Project Settings tab, you can:
- Connect to a Klocwork Server project
- Specify the location of your Klocwork Build SpecificationNote: Make sure your build specification file is always kept up-to-date when you add, move, and/or remove a file to ensure accurate analysis results.
- Enable use of Klocwork Server Build Specification template(s) and set specific variables.
- Disable parallel analysis
- Use 32-bit analysis tools - In some situations, you may want to force Klocwork to use 32-bit analysis. For example, if you want to use 32-bit checkers (that is, checkers compatible with a pre-2020.3 version of Klocwork), you must select this option.
Change server settings
Typically, server information is set during installation. However, when this information changes, you need to update it. In the Settings > Tools > Klocwork System Settings tab, you can:
- Set the Klocwork User Installation location.
- Set the host and port information for the Klocwork Server.
- Specify a secure connection to the Klocwork Server.
- Specify the host and port information for the License Server.
- Disable continuous analysis
Locate system issues
For connected desktops, you may need to investigate or fix a system issue. Klocwork Static Code Analysis provides a System ID for each detected issue. By default, the connected desktop does not identify issues by System ID in the issue list.
To locate a system issue:
- Obtain as much information about the issue as you can, such as the file in which the issue is located, issue type (ABR, for example), line number, owner (if applicable) and severity.
- Make sure the "Show Local issues only" setting is toggled off.
- If you know what module the issue is in, as well as the file name and issue type, then group by file and issue code. In the Klocwork Issues tab, make sure the following grouping controls are selected: File Issue type
- View the contents of the Issue type group to find the right system issue.
View an issue's history
You can view the status and comment history for selected issues in the Klocwork Issues tab.
Right-click an issue in the Klocwork Issues tab and select Status history.
The Status History dialog displays the history of issues detected in a connected desktop project. The name of the user who made the changes and the date and time of the edits are included. The date and time of the initial status of Analyze are always noted first.
If you are connected to a server project but synchronization is disabled and you have not yet synchronized manually, or your project is in standalone mode, only your latest status change is displayed.