Start here

Home
About Klocwork
What's new
Fixed issues
Release notes
Installation

Reference

C/C++ checkers
Java checkers
C# checkers
MISRA C 2004 checkers
MISRA C++ 2008 checkers
MISRA C 2012 checkers
MISRA C 2012 checkers with Amendment 1
Commands
Metrics
Troubleshooting
Reference

Product components

C/C++ Integration build analysis
Java Integration build analysis
Desktop analysis
Refactoring
Klocwork Static Code Analysis
Klocwork Code Review
Structure101
Tuning
Custom checkers

Coding environments

Visual Studio
Eclipse for C/C++
Eclipse for Java
IntelliJ IDEA
Other

Administration

Project configuration
Build configuration
Administration
Analysis performance
Server performance
Security/permissions
Licensing
Klocwork Static Code Analysis Web API
Klocwork Code Review Web API

Community

View help online
Visit RogueWave.com
Klocwork Support
Rogue Wave Videos

Legal

Legal information

Filtering issues on the desktop

Filtering issues on the desktop

Filtering allows you to narrow the scope of the issues listed in the Klocwork Issues view. For example, you can limit your issue list to those:

  • in a particular taxonomy
  • in the selected file or directory
  • of local origin (that is, issues you've introduced into the code)
  • of the highest severity
  • in currently selected file(s)
  • of a particular status
  • belonging to a particular owner
  • in a selected working set (Klocwork Desktop only)
Tip: Filtering by taxonomy allows you to focus only on violations of a particular standard, such as MISRA C or MISRA C++, or by custom checker groupings that have been applied to the integration project.

Filter settings remain in effect for the project until you change them again. So, if there are issues that are missing from your list, check and adjust your filter settings to see more issues as desired.

Filtering settings differ among the IDE plug-ins, Klocwork Desktop, and kwcheck. See the how-to links provided below.

Issue citing

Issue citing is another way of filtering your detected issues. For example, changing an issue's status to Ignore indicates that this issue was found in code that you don't care about.

The default status filtering shows only issues in Analyze and Fix status. Use "Not a Problem" status to handle isolated false positives for a particular issue type (for example, CL.FFM.ASSIGN).

On the other hand, if there's an issue type that you really don't care about, you can disable it using the Configuration Editor, which is an entirely different activity from filtering. Enabling and disabling issues is one way of customizing your analysis.