Release Notes

From current

Contents

These release notes cover Klocwork Insight 9.5 SR1 and Klocwork Inspect 2.5 SR1. For new features in this version, see What's New.

Changes affecting migration

This section details product changes that affect how Insight data is migrated from a previous version. For general information on upgrading, see Upgrading from a previous version.

Severities: Checkers are now assigned only severities 1 through 4 by default. Ten severity levels are still available, and it is still possible to edit the severity level for any checker. The default labels for all severity levels have changed. Custom checkers are now assigned severity 4 by default.

After migration, before you run your first version 9.5 analysis, you will still see 10 severities. Once you have run the first integration build analysis for a project with 9.5:

  • all issues whose severity was not customized have severities 1 through 4.
  • all issues with non-default severities keep the custom severities.

Note that you need to run an analysis on each of your projects to see the change in severities.

This change may cause a significant increase in the number of high-severity issues detected in version 9.5. For a mapping of severities between the two versions, contact Klocwork Customer Support.

Details: Issue severity and Changing issue severities

States: The states Not in scope, Recurred and Obsolete have been removed in this version. You can compare builds in Klocwork Review to find issues formerly labeled with these states. We recommend running your final pre-upgrade analysis and your first 9.5 analysis on identical source code, and then comparing the two builds, so that you can properly assess the changes in your analysis results due to improvements in our analysis engine.

Details: Issue states

Scopes: The concept of "scopes" has been replaced by views. Existing scopes are converted to views during migration to version 9.5. Note that if a scope from a previous version contained an Insight Architect user model, the user model information is not included in the version 9.5 view, because user models are no longer displayed in Klocwork Review.

Details: Help - I'm used to scoping in Klocwork Review

Custom reports: In previous releases, the metrics.xml file has two report definitions: "Size" and "Complexity". These reports were special in that they needed to be defined in metrics.xml in order to show up in Klocwork Review, but any modifications to those reports in the file were ignored, because Insight used special implementations when loading "Size" and "Complexity". In version 9.5, these two reports are no longer treated specially and will show up as duplicates in the report type selector page. The migration disables them in the metrics.xml file. Any other migrated custom reports appear in the report type selector page as expected.

Details: Reporting for the integration build and Customizing metrics reports in Klocwork Review

Reports based on components: The concept of "components" has been replaced with "modules". The titles of reports using "component" are not changed during migration.

Details: Organizing your code into modules and Reporting for the integration build

Modules.xml file: The modules.xml file is no longer supported. You now control access to source code with modules in Klocwork Review. Existing modules.xml files are converted to modules during migration to version 9.5. Modules that cannot be converted are reported in kwmigrate.log.

Details: Organizing your code into modules

Roles: Three new roles exist in this version: Build engineer, Developer and Manager. However, these roles do not exist by default for migrated projects_roots.

Details: Enabling access to Klocwork projects

Visual Studio: Local defects are not migrated from previous versions.

Changes to licensing

  • Fixed user licenses are now referred to as "individual" licenses. In new licenses issued for version 9.5, individual licenses have a linger time of 24 hours. Floating user licenses are now referred to as "global" licenses; the linger time is still 10 minutes. See How licensing works.
  • If you used the Klocwork Stack Overflow Analyzer for C/C++ (kwstackoverflow) in a previous version, contact Klocwork Customer Support for an updated license.
  • Klocwork Refactoring is now included as a part of the Insight package. The refactoring keyword is no longer needed for licensing because it is now a part of the standard Insight package.

Details: How licensing works

Changed and removed commands and options

The following table lists changed and removed commands in this release. For more detail on Klocwork commands, see Command Reference.

Important: These changes can affect existing scripts.

Command Details
kwadmin create-branch Subcommand has been deprecated. Use kwadmin duplicate-project instead. See Managing project branches for how-to information.
kwadmin create-project The --language option has been removed. The language is now automatically detected from the source files and set for the project.
kwadmin create-project
kwadmin load 		The --copy-sources and --no-copy-sources options have been removed. Source files are now always copied to the projects_root directory after the analysis.
kwadmin create-project
kwbuildproject
kwecbuild
kwconv 		The --source-encoding option, used to encode the source files used in a project, has been renamed to --encoding.
kwcheck run The quiet argument for the -F option was removed from the documentation because it was an internal argument, not meant to be documented. Instead of using -F quiet, the best practice is to:
  • focus the analysis on a smaller subset of your project
  • focus the analysis on newly introduced defects (the default behavior) rather than the entire system
  • use filtering options to filter the displayed list by taxonomy, severity, issue type, or status
kwstackoverflow This command is now included only in the Klocwork User package.
kwuser The update process for LDAP with kwuser is no longer needed. Users/groups are now taken directly from the LDAP server.

Changes to system requirements

This section lists changes to the System requirements.

Added

Platforms

  • Mac OS X Lion (10.7)
  • Fedora Core 14, 15
  • Red Hat Enterprise Linux 5.x, 6.x
  • Open SUSE 11.4
  • Debian 6.0
  • Ubuntu 10.10, 11.04, 11.10

IDEs

  • IntelliJ IDEA 10, 10.5
  • Eclipse 3.7
  • Eclipse 64-bit support for Windows and Linux

Java

  • 64-bit Java support for Windows and Linux

Browsers

  • Firefox 9
  • Internet Explorer 9
  • Google Chrome 15
  • Safari 5 & 5.1

No longer supported

Platforms

  • Fedora Code 11, 12 & 13
  • Open SUSE 10.3, 11.2
  • Debian 4.0
  • Ubuntu 6.06, 9.10
  • Mac OS X Leopard (10.5)

IDEs

  • Nokia Carbide.c++

Browsers

  • Internet Explorer 6 & 7
  • Safari 4

To be removed in the next release

kwinspectreport XML output and Klocwork Review XML export are still available in version 9.5 but will be removed in the next release. These capabilities have been replaced by the Klocwork Web API.

Changes affecting existing users

This section details changes that you should be aware of if you've used a previous version of Insight. See also What's New for a summary of major new features in this version.

Klocwork Management Console (KMC) removed

Most functionality previously found in the Klocwork Management Console (KMC) has been moved into Klocwork Review, with the exception of the following:

All other KMC functionality can now be accessed through Klocwork Review. See Getting started with Klocwork Review.

Changes to the Configuration Editor

You now access the Configuration Editor from the project management area of Klocwork Review.

The UI has been changed to distinguish between configuring the analysis itself and configuring the presentation of the analysis data. The Categories tab has been replaced by two new tabs: Analysis Profile (for enabling/disabling of checkers) and Taxonomies (for editing taxonomies, categories, severities and "reference" metainfo).

Previously, checkers were highlighted in blue when either the enable/disable state or the severity was changed. In version 9.5, blue indicates only a change to the enabled/disabled state and is used only on the Analysis Profile tab.

The database is now updated immediately when you save changes in the Configuration Editor; there is no prompt to confirm the update.

See Configuring checkers for the integration build analysis for details on both project-specific and global checker configuration.

Changes to Klocwork Review

Besides what is covered in What's New, note the following:

  • The concept of "scopes" has been replaced by views. See Help - I'm used to scoping in Klocwork Review.
  • The Header Analysis feature has been removed from Klocwork Review in Insight 9.5. With the introduction of Header Analysis refactoring, our focus has switched from reporting header problems to preventing them. For more information, see Klocwork Refactoring.
  • You can search by group in Review with the 'owner:' keyword. For more information, see Searching in Klocwork Review.
  • The file model is now the default model type for Java projects in Review. The package model is still available in Klocwork Architect.

Changes to access control

  • User, role and permissions management has been moved to Klocwork Review. See Enabling access to Klocwork projects.
  • The modules.xml file has been deprecated. You now control access to source code with modules in Klocwork Review. Existing modules.xml files will be converted to modules during migration to version 9.5. See Organizing your code into modules. Modules that cannot be converted are reported in kwmigrate.log. Note that users still require the "Access source files" permission in addition to module permissions.

Changes to Klocwork Inspect

  • kwscm now loads all revisions from your SCM, unless you specify what revisions to load. After the first run of kwscm, we recommend loading specific revisions to improve performance. For details, see kwscm.
  • Running both kwscm and kwcodereview feels more like running your SCM command: we've introduced SCM-specific options, so that you can specify ClearCase branches, for example, or CVS tags. To facilitate this tighter integration with your SCM, kwscm and kwcodereview now require you to specify your SCM as an argument.
  • The option to incrementally load 30 lines of code within Inspect's diff view has been removed. Instead, the diff view shows you all of the changes made in the most recent revision. There is still the option to show full source.

Changes to desktop analysis

  • System issues (those detected in the integration build analysis) are no longer displayed during initial synchronization, which occurs when you connect to the integration project.
  • Eclipse C/C++ plug-in users: We no longer recommend that you rely on the Eclipse CDT Indexer to generate your build settings. This method has been proven inaccurate. Instead, use kwinject to capture build settings, either directly, or by prefacing your build command with kwinject. For details, see Getting started with Klocwork Desktop C/C++ Plug-in for Eclipse.
  • Visual Studio C/C++ plug-in users: The analysis now runs as you type, rather than only on opening or saving a file. The Visual Studio plug-in no longer supports the following:
    • importing/exporting user profiles
    • usage rules (the Rules File field)
    • metric thresholds (the Metrics File field)
    • macro override files (the Override File field)
    • managing knowledge base files (the Manage button)
    • use of external build specifications
    This type of configuration should now be done on the server. System knowledge base files, checker configuration and override files are passed to Visual Studio during synchronization. For details on using the C/C++ plug-in for Visual Studio, see Getting started in Visual Studio for C/C++ projects.

Changes to compiler configuration

  • We no longer advise that you try to configure custom compilers yourself. Instead, we are committed to providing this configuration for any C/C++ compiler that you need, with Python scripts (*_filter.py). As a part of this change, the *_filter.xml files are obsolete and no longer used. Note that these Python scripts are not meant to be edited. See Adding an unsupported C/C++ compiler for more information.
  • The compiler configuration file kwcc_config.xml is obsolete.

Changes to cross-project synchronization

  • A new option, --full, has been added to kwxsync. This option forces a full synchronization (by default, kwxsync works in incremental mode).

Changes to Klocwork Extensibility

Known limitations

Limitations for installation, upgrade and deployment

Some virus scanners may slow analysis performance

If certain virus scanners are deployed (such as Trend Micro Worry-Free Business Security 6.0), your analysis time may increase.
Workaround: If your anti-virus software permits, configure exclusion folders for the projects_root directory and the tables directory.

Interoperability between releases

Insight clients earlier than Klocwork Insight 9.5 cannot interoperate with a Klocwork Insight 9.5 Server. You must upgrade both your Server and User installations. See Upgrading from a previous version.

Use caution when installing Klocwork Insight 9.5 User package on a machine that hosts a previous version of Klocwork Insight

If you install the Klocwork Insight 9.5 User package on a machine that already hosts a previous version of Klocwork Insight, the Klocwork Insight 9.5 plug-ins for Visual Studio and IntelliJ IDEA will overwrite the previous version of the Klocwork Insight plug-ins. If you want to continue to use the previous version plug-ins, skip installation of the Klocwork Insight 9.5 plug-ins by choosing the Custom method during installation. For Unix, you can prevent installation of the IntelliJ IDEA plug-in by not specifying the --idea-dir option during installation.
To upgrade these plug-ins to Klocwork Insight 9.5 at a later date:
  • Windows: Go to the Add or Remove Programs Control Panel, select Klocwork Insight 9.5 User, and click Change. When prompted, select Modify. On the Custom Setup screen, make sure This feature will be installed on local hard drive is selected for the plug-ins you want to install.
  • Unix: Reinstall the Insight 9.5 User package and specify the --idea-dir option to install the IntelliJ IDEA plug-in. See Installing the Klocwork User package on Unix.

Only one set of Klocwork Insight 9.5 Servers can be run as Windows Services on each host

It is not possible to run two sets of the Klocwork Servers as Windows Services on one host when the servers are of the same Klocwork version.
Workaround: Start additional instances of the Klocwork Insight 9.5 servers using kwservice (and set the ports appropriately, so that there is no conflict).

Users may not be able to connect to the Klocwork Servers if Server host machine is brought out of hibernation mode

Windows only, when not running Klocwork Servers as Windows Services: Users may not be able to connect to the Klocwork Servers if the machine hosting the Klocwork Servers is brought back from hibernation mode. Restarting the Klocwork Servers does not help this problem.
Workaround: Log off the machine hosting the Klocwork servers and log in again, or restart the server host machine. Alternatively, run the Klocwork Servers as Windows Services.

Remote Klocwork clients may not be able to connect when Klocwork Servers are started on "localhost"

Linux and Solaris only: If you start the Klocwork Servers on a machine where the /etc/hosts file contains an alias that maps the host name to localhost address 127.0.0.x, remote Klocwork Insight clients will not be able to connect to the servers.
Workaround: Remove the alias to 127.0.0.x from /etc/hosts and restart the servers.

Projects_root directory cannot be located on a shared file system (NFS)

Unix only: Due to MySQL limitations, the projects_root directory should not be located on NFS. It has a special file locking implementation which is not fully supported by MySQL. See also the warning in the MySQL documentation.

NIC naming convention em[123...] not supported

The NIC naming convention on Fedora Core 15 is em[123...] by default, which is not supported by Insight.
Workaround: Configure NIC as eth[0123...], which is supported by Insight.

Limitations for Mac OS X support

  • Distributed Analysis is not supported.
  • For developers, plug-in support is provided for Eclipse and IntelliJ IDEA. If your developers are not using Eclipse or IntelliJ IDEA, they need to use Klocwork Desktop Command Line for C/C++ or Java (kwcheck) or Klocwork Desktop to analyze their code and view detected issues. See Fixing issues before check-in with Klocwork Desktop Analysis.

Limitations related to internationalization

See also Klocwork support for non-ASCII encoding.

Installation path cannot contain multibyte characters on Unix

If you attempt to install to a path containing multibyte characters on Linux, Solaris or AIX, the installer package will exit with an error message.
Workaround: Ensure that the path to the chosen installation directory contains only ASCII characters.

Unix, using dash: Cannot start servers on projects_root containing non-ASCII characters

When using dash (the default shell on Ubuntu), it is not possible to start the Klocwork Servers on a projects_root with Japanese characters in the path. This is due to a dash limitation related to improper handling of multibyte characters.
Workaround: Use a different shell, for example bash.

Limitations for build integration

Must specify full path to devenv when running kwinject in 4NT shell

Even if the Microsoft Visual Studio build command devenv is in your path, kwinject will not produce a build specification when run in a 4NT shell unless you specify the full path to the devenv tool. 4NT is a non-default command shell for Windows.
Workaround: Specify the full path to devenv when running kwinject in a 4NT shell.

Limitation for support of IAR Systems C compiler

Klocwork Insight does not process the following compiler option for the IAR Systems C compiler, icc8051:
-G. Opens standard input as source, instead of reading source from a file.
Workaround: If your build uses this option, there are two alternatives:
  • Ignore these compilations. The code that is being piped through standard input will not be analyzed in the Klocwork build (this is what kwinject does by default).
  • Save the source code to a file and run icc8051 with the source file as input.

Cannot specify symbolic link as command when running kwinject under Cygwin

When running kwinject under Cygwin, it is not possible to specify a symbolic link as the command argument for kwinject.

Limitations for Klocwork analysis

Limitations for C# analysis

Klocwork's C# analysis is supported only on Windows.

Writing custom checkers is not supported for C# projects.

The following features are not supported for C# integration projects:

Feature Details
Build integration
Integration build analysis
Klocwork Review
Distributed analysis Distributed analysis is not supported for C#.
Architecture redesign Klocwork Architect is not supported for C#.

The following features are not supported for C# desktop analysis:

Windows Indexer or antivirus program accesses temporary MySQL files, causing table loading to fail

During the table-loading phase, MySQL makes temporary files. If Windows Indexer is running or your antivirus program is running a real-time scan, these programs may try to access your temporary MySQL files, locking them, and causing table loading to fail.
Workaround:

Create a separate directory to contain temporary MySQL files, and then:

  1. Configure Windows Indexer or the antivirus software to ignore the directory.
  2. Access the non-default MySQL configuration file, located at:
    <Server_install>/config/kwmysql.ini
  3. In the <kwmysql.ini> file, add:
    tmpdir=<path_to_exempt_directory>
    Note: Backslashes should be doubled when specifying a Windows folder path. Windows example: "C:\\temp\\exempt"
  4. Restart the Klocwork Database Server.

For projects containing JSP files, specifying a Windows UNC path to the tables directory generates error

When analyzing a project containing JSP files, if you specify a Windows UNC path to the output tables directory (for example, \\ComputerName\SharedFolder\Resource), you may see errors such as "No Java files were created by jsp converter". This is due to an Apache Tomcat limitation.
Workaround: Specify a non-UNC path to the tables directory (map the network share to a drive).

"Tracker" plug-in for GNOME may cause performance drop in full analysis

Unix only: Running the Tracker search tool for GNOME may significantly slow a full Klocwork analysis.
Workaround: Disable Tracker when running a Klocwork analysis.

Database loading phase may fail if using IPv6

kwadmin may generate the message "Database loading stage failed" during the database loading phase if you are using IPv6.
Workaround: Add the fully qualified host name to the database.host property. To do this:
  1. Open <projects_root>/config/admin.conf in a text editor.
  2. Add the fully qualified host name to the line beginning database.host=. For example:
    database.host=myserver
    should be changed to:
    database.host=myserver.klocwork.com
  3. Restart the Klocwork servers.
  4. Restart the Klocwork analysis.

Limitations for Klocwork Desktop Analysis

Limitations for the Eclipse plug-ins

Toolbar on Klocwork Insight views doesn't display properly on 64-bit Ubuntu

Versions of 64-bit Eclipse previous to 3.5.3 may not display tools such as Configure filters on Klocwork Insight views on Ubuntu.
Workaround: Close and re-open Eclipse.

Eclipse 3.6.0 with LDAP crashes if Reviewers field is clicked after selecting a reviewer name

When using LDAP access control: If you type a partial user name in the Reviewers edit box in the Create Code Review dialog, the matches are displayed in a box. If you then select a user from that list with a single click and proceed to click the Reviewers edit box, Eclipse will crash.
Workaround: Upgrade to Eclipse 3.6.1 or later to solve this issue, or use the arrow keys and Enter to select a reviewer.

Limitations for Klocwork Desktop

Project name not saved when using non-default location

When creating a project in a non-default location, the project name is not saved.
Workaround: Repeat your project name in the Project Location field.

Limitations for Klocwork Extensibility

C/C++ Path checker compilation makefile compatibility

The makefile generated by kwcreatechecker on Unix systems requires GNU make to build the checker. The default make installed on non-GNU systems such as AIX or Solaris may not compile Klocwork extensions for C/C++. On Windows, the makefile generated by kwcreatechecker requires nmake to build the checker.
Workaround: None.

Checker Studio cannot represent non-standard header files

Errors will be printed in the Output window of Checker Studio when the AST is generated for source code that contains non-standard header files.
Workaround: Use self-contained examples that do not rely on external includes in Checker Studio.

Analysis fails if Java KAST custom checker was built using a version 1.7 JDK

If you use JDK version to build custom Java KAST checkers, the Insight analysis will fail during the kwjava phase:
Tue Jan 10 11:19:54 EST 2012: Running Java compilation stage...
Error occurred during build: kwjava returned 1
Workaround: Build Java KAST checkers using JDK version 1.6.

Limitations for Klocwork Review

Multi-word entity search highlighting not supported

Entity highlighting in the Source Viewer works only for single words.
Workaround: None.

Issue status change history difficult to view if user name is very long

If a user's name is very long, the status change history dialog spills outside the browser window.
Workaround: None.

Header Analysis in Klocwork Review no longer supported

Klocwork Insight 9.2 was the last release in which Header Analysis was supported. With the introduction of Header Analysis refactoring in Eclipse, our focus is switching from reporting Header Analysis problems to preventing them. For more information, see Klocwork Refactoring.

Internet Explorer cannot list project names if Klocwork Server host name contains underscore

Klocwork Review uses cookies to handle session authentication. Internet Explorer will not save cookies for domains containing an underscore.
Workaround:
There are three options:
  • Change the Klocwork Server domain name to use only alphanumeric characters
  • Have Internet Explorer users open Klocwork Review using the IP address of the Klocwork Server
  • Create a domain alias for Internet Explorer users

Klocwork Review and Klocwork Inspect user names are case sensitive

If the Klocwork Server is running on a Windows machine, users who log in to Klocwork Review and Klocwork Inspect have a license checked out using the lowercase form of their user name. Other tools such as Klocwork Architect will not change the case of the user name (obtained from the OS), so a second license is checked out.
Workaround: Use a lowercase user name.
If the Klocwork Server is running on a non-Windows machine, users who log in to Klocwork Review and Klocwork Inspect have a license checked out using the case as entered in the Login dialog. As above, other Klocwork tools use the user name as obtained from the OS.
Workaround: Match the user name case used by your OS.

Can't edit custom folder names for Klocwork Review reports

If you create a report and put it in a new folder, there is no way to rename that folder later.
Workaround: If there is a single report in that folder, click edit for the report and change the folder name. If there are multiple reports in the same folder, repeat this for each report until they have all moved to the new folder. Once they have all been moved, the old folder will disappear from the list.

Can't view Klocwork Review video in Internet Explorer over SSL

If you're if using a secure connection to the Klocwork Server and you're logged in to Klocwork Review using Internet Explorer, it's not possible to view the embedded video.
Workaround: Try another supported browser.

Limitations for Klocwork Inspect

Setting up post-checkin review on Unix with kwscm hangs if using Subversion client with gnome-keyring support

When using a Subversion client with gnome-keyring support on Unix (starting with Collabnet Subversion v1.6), kwscm will hang.
Workaround 1:
Disable gnome-keyring for your Subversion client. To do this, open the file ~/.subversion/config, find the [auth] section and add the following text:
[auth]
password-stores =
Workaround 2:
Use a Subversion client compiled without gnome-keyring support.

Diff view fails to load; Subversion message "Server certificate verification failed"

If the Klocwork Servers are run as Windows Services under the default user (the Local System account), when trying to view a diff, you may see the following message:
"Server certificate verification failed; certificate has expired, issuer is not trusted."
Workaround:
  1. Run the Klocwork Servers as Windows Services under a non-default user account. To learn how, consult the Microsoft Windows Services documentation.
  2. Make sure that under the new user account, Subversion command-line utilities work in non-interactive mode. That is, either SSL certificates must be accepted permanently during an interactive Subversion command execution, with a valid user name and password, or SSH authorization must be configured.

Subscribing to RSS feed with Microsoft Outlook fails when using a secure Klocwork Server connection (https)

When Klocwork is set up to use a secure connection, if you subscribe to Klocwork Inspect feeds with Microsoft Outlook via RSS, content fails to download because of a problem connecting to the server.
Workaround: None.

Limitations for user documentation

Some links in online help return a "Cannot display the web page" error if not connected to internet

In Eclipse, Visual Studio, and Klocwork Desktop, if you are not connected to the internet, clicking on some links in the online help will return a "Cannot display the web page" error. To reduce the size of the online help file, not all help pages are packaged with these tools.
Workaround: Connect to the internet to view these pages in the Documentation Wiki.

Documentation Wiki does not remember user login in other browsers

If you have logged in to the Wiki and you open another session (in another browser, or from your IDE), the Wiki will not know that you have already logged in.
Workaround: Log in again.

Must enable cookies in Internet Explorer to log in to Documentation Wiki from Eclipse plug-in or Klocwork Desktop on Windows

Windows only: If you do not have cookies enabled in Internet Explorer, you will not be able to log in to the Documentation Wiki from the plug-in for Eclipse or from Klocwork Desktop. Note that login is required only for editing pages on the Doc Wiki.
Workaround: Because Eclipse and Klocwork Desktop use Internet Explorer for help browsing, you need to enable cookies in Internet Explorer.

URLs to external sites don't work in the help for Klocwork Architect and IntelliJ IDEA

It's not possible to navigate to external URLs from the help in Klocwork Architect, or IntelliJ IDEA.
Workaround: Use the Documentation Wiki at http://www.klocwork.com/products/documentation/Insight-9.5/ to navigate to these pages.

PDF links don't work in the help for Klocwork Architect and IntelliJ IDEA

If you click a link to a PDF in the help for Klocwork Architect or IntelliJ IDEA, the file name displays as a title in the right pane, but there's no text. This is an issue for users trying to access the C/C++ extensibility reference manuals.
Workaround: You can access the Klocwork C/C++ AST API Reference and Klocwork C/C++ Path API Reference PDFs from the Reference page on the Documentation Wiki.

Help links for detected issues don't work in IntelliJ IDEA 10.5 and 10.5.1

If you click Show help for a selected defect in IntelliJ IDEA 10.5 or 10.5.1, an error is shown.
Workaround: Use the Documentation Wiki at http://www.klocwork.com/products/documentation/Insight-9.5/ to find the help for the defect that you need more information about.
Retrieved from "http://www.klocwork.com/products/documentation/current/Release_Notes"