Release Notes

From current

Insight 9.6

Contents

These release notes cover Klocwork Insight 9.6 and Klocwork Inspect 2.6. 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.

Windows User package: The installation package now automatically detects whether you have a previous version of the User package installed and uninstalls it before installing the newest version. There is no need to uninstall the User package before you upgrade.

Japanese for migrated projects: To display Japanese issue messages, traceback and context-sensitive issue help for a migrated project, set the "locale" project property to "ja" with the kwadmin set-project-property command. Then, run kwbuildproject with the --url option so that the project properties are used in the analysis. Note that Insight will display Japanese issue messages and traceback only for issues that are detected in a Japanese build (that is, a build run on a machine with the system locale set to Japanese). Other issues will remain in English (until they are detected in a Japanese build).

Disabled checkers: Make sure you have the same checker configuration as in the last release before your first version 9.6 integration build analysis.

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
kwinspectreport
  • The --xml and --text output options have been removed.
  • The --state and --status output options have also been removed because these were only supported for --xml and --text.

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.

Japanese version of Insight

Klocwork Insight tools and documentation are now available in Japanese. See What's New for more details.

Licensing changes

Insight 9.6 now supports FLEXlm server version 11.10.1.0 for all platforms. If you use your organization's FLEXlm license server, you need to upgrade to this FLEXlm version. See Using your organization's FLEXlm server.

Changes to Klocwork Review

  • You can now integrate your bug tracking system with Klocwork Review. See Bug tracker integration for more details.
  • The Configuration Editor can be accessed from Klocwork Review in your web browser. See What's New for more details.
  • Klocwork Review now has a user profile similar to the one in Inspect, which is accessible from the avatar menu. See What's New for more details.
  • You can set up Review so that you're notified by email whenever new code issues appear after a system build. See What's New for more details.
  • The --xml and --text output options have been removed. These capabilities have been replaced by the Klocwork Web API.

Changes to Klocwork Inspect

  • You can set up Inspect so that you're notified by email when an action occurs or a comment is received for an issue, or when a code review invitation or feedback message is issued. See What's New for more details.
  • We have made improvements to code reviews, including the ability to set a base revision. See What's New for more details.

Changes to access control

The Windows Single Sign-on feature allows users who are logged in to Windows to be automatically logged in to the Klocwork portal, plug-ins, and standalone clients. See What's New for more details.

Changes to desktop analysis

Changes to the Configuration Editor

  • Klocwork Review: We've added the ability to access the Configuration Editor in the web browser. This allows you to enable and disable checkers for a project in Review. Context-sensitive help is now provided for all checkers.
  • Visual Studio C/C++ plug-in users: The Configuration Editor can now be accessed right from the Klocwork Properties menu.

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.6 cannot interoperate with a Klocwork Insight 9.6 Server. You must upgrade both your Server and User installations. See Upgrading from a previous version.

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

If you install the Klocwork Insight 9.6 User package on a machine that already hosts a previous version of Klocwork Insight, the Klocwork Insight 9.6 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.6 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.6 at a later date:
  • Windows: Go to the Add or Remove Programs Control Panel, select Klocwork Insight 9.6 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.6 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.6 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.6 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 and localization

See also:

Japanese version of Insight

The following are not localized in Insight 9.6:
  • Insight Architect (tool and documentation)
  • the IntelliJ IDEA plug-in (because IntelliJ IDEA does not provide a Japanese version of the IDE)
  • The MISRA checker help, because MISRA does not provide a translated version

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. This problem exists for Ubuntu 10.10 only.
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.

Build specification generated with kwinject in Insight 9.6 is incompatible with Insight 9.5

Build specifications generated using Insight 9.6 are incompatible with the analysis engine from previous releases. This is due to a new option (--type-sizes) that kwinject adds to the configuration line of the build spec that earlier versions of the Klocwork compiler, kwcc, can't understand.
Workaround: Generate build specifications using the same version of Klocwork Insight that you will be using to run the analysis.

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 Visual Studio plug-in

Klocwork C/C++ compiler does not parse files compiled with /CLR option

Visual Studio 2005 and 2008 allow you to create a C++ project with files that use Microsoft's managed C++ extensions. The Klocwork C/C++ compiler (kwcc) does not parse files compiled with the /CLR option. It issues a warning that the compiler skipped parsing of these files because of the use of managed extensions. This warning is included in build summary statements that count warnings and errors.
The build specification tools kwvcprojparser and kwinject add entries for all C++ files, but they report the number of files that will be skipped during an analysis (if any), as well as the total number of files added to the build specification.

The following limitations are only seen when you make external modifications outside of the Visual Studio environment:

Defects disappear from the issue list when undoing changes

If you undo your changes to the point where the file was reloaded, your list of defects may disappear. This problem only occurs in Visual Studio 2005/2008.
Workaround: The file must be re-opened if modified externally.

Ignored defects reappear in the issue list as active issues

If a file is modified externally and the defect is shifted from its original location, defects with the status of Ignored will reappear in your issue list within Visual Studio.
Workaround: None.

Duplicate defects appear in the issue list

If a file is modified externally and changes to the file are reloaded, all of the defects are removed and re-detected. There are cases where the defect is not synched back to the server and the issue remains local rather than synched with the appropriate system issue. Therefore, duplicated sandbox defects may appear on the server, causing sync to not perform as expected. This problem only occurs in Visual Studio 2005/2008.
Workaround: The file must be re-opened if modified externally.

Defect citation is lost after corresponding source is renamed

If a defect is cited and then the corresponding source file is renamed, the status may be lost when you perform your next analysis. The status is only lost if the parent of the defect is changed. In other cases, the status is still preserved.
Workaround: None.

If a source file is renamed, then changed back to its original name, defects will no longer be detected for that file

If a source file is renamed to a name that it previously had, the defects related to it will disappear. Running analysis again will not fix the issue. This problem is seen for both on-the-fly and on-demand analysis.
Workaround: To fix this issue, close the file and re-open it. The proper defects will now be seen as expected.

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 the IntelliJ IDEA plug-in

IntelliJ IDEA plug-in not available in Japanese

IntelliJ IDEA is not localized for Japanese, so the Insight plug-in for IntelliJ IDEA is not available in Japanese. Likewise, the Japanese documentation is not available from the IntelliJ IDEA plug-in.
Workaround: To access the Japanese documentation, go to http(s)://<klocwork_server_host>:<klocwork_server_port>/, select ja in the drop-down menu, open Klocwork Review and click Help. Or use the Japanese Documentation Wiki.

Cannot access issue help from IntelliJ IDEA 11.1.1 or 11.1.2

Issue help for IntelliJ IDEA 11.1.1 and 11.1.2 cannot be accessed by right-clicking an issue in the issue list and selecting Show help or by pressing F1.
Workaround: IDEA bug that blocks access to third-party plug-in help, such as that provided by Klocwork Insight, has been fixed by JetBrains in version 11.1.3, details available at http://youtrack.jetbrains.com/issue/IDEA-87389. Previous versions of IntelliJ IDEA appear unaffected.

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 Architect

Architect menu isn't visible in Ubuntu 10+

A problem with the default "Ambiance" theme in Ubuntu 10+ means that the Klocwork Architect menu isn't visible.
Workaround:
  1. Switch from the Ubuntu Ambiance theme to the Radiance theme.
  2. Copy the Ambiance theme into your home directory from /usr/share/themes to ~/.themes.
  3. Edit file /home/<username>/.themes/Ambiance/gtk2.0/gtkrc, replacing the line
style "menu" {
with
style "menu" = "dark" {

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 <tt>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.

Cannot use the Remember me option on a server with multiple server instances

If you are running multiple server instances on the same server (for example, klocwork.example.com:8080 and klocwork.example.com:8072) and log in to each server with different credentials (for example, you use jsmith to log into the server on port 8080 and jdoe to log into the server on port 8072), the "Remember me" feature does not work properly. The authentication key is stored in a browser cookie and can only be stored for a domain (the port cannot be specified).
Workaround:
There are two options:
  • For the first server, access the site using the normal domain name (for example, jdoe1.klocwork.com:8080); on the second, use the IP address of the Klocwork Server instead of the domain name (for example, 10.0.145.7:8070).
  • Set up a domain alias for the second server (either locally via your hosts file, or by setting it up globally).

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.

Can't search for Severities in Klocwork Review

If your saved searches for severities appear in the wrong language, the search will not display the expected results.
Workaround: Log in to portal with the locale used during the project build and your saved searches will update to the correct language. Searching for severities will now work as expected.

Middle-clicking a link doesn't open it in a new tab when using Google Chrome

Due to a bug in Google Chrome, some links do not open in a new tab when they are middle clicked, shift-clicked or ctrl-clicked after the first time the link is opened in this manner. Each successive attempt simply opens the link within the active tab. For more information, see http://code.google.com/p/chromium/issues/detail?id=177502
Workaround: Refresh the page and this will allow you to open the link in a new tab the first time you attempt it.

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.

Cannot use the Remember me option on a server with multiple server instances

If you are running multiple server instances on the same server (for example, klocwork.example.com:8080 and klocwork.example.com:8072) and log in to each server with different credentials (for example, you use jsmith to log into the server on port 8080 and jdoe to log into the server on port 8072), the "Remember me" feature does not work properly. The authentication key is stored in a browser cookie and can only be stored for a domain (the port cannot be specified).
Workaround:
There are two options:
  • For the first server, access the site using the normal domain name (for example, jdoe1.klocwork.com:8080); on the second, use the IP address of the Klocwork Server instead of the domain name (for example, 10.0.145.7:8070).
  • Set up a domain alias for the second server (either locally via your hosts file, or by setting it up globally).

If your Perforce server is not in unicode mode and the user's P4CLIENT contains non-ASCII characters, kwcodereview may fail

This is due to a bug in the Perforce P4Java API. When the Perforce client (P4CLIENT environment variable or --client option to kwcodereview) has non-ASCII characters in it.
Workaround
There are two options:
  • Only use clients with names having ASCII (byte value < 128) characters
  • Convert your server to unicode

Middle-clicking a link doesn't open it in a new tab when using Google Chrome

Due to a bug in Google Chrome, some links do not open in a new tab when they are middle clicked, shift-clicked or ctrl-clicked after the first time the link is opened in this manner. Each successive attempt simply opens the link within the active tab. For more information, see http://code.google.com/p/chromium/issues/detail?id=177502
Workaround: Refresh the page and this will allow you to open the link in a new tab the first time you attempt it.

Limitations for user documentation

Documentation for C/C++ custom Path checkers

Documentation for custom C/C++ Path checkers is not provided on this site. If you think you need to create a custom Path checker for C/C++, please contact Klocwork Customer Support so that we can guide you in the creation process and provide 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.

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/current/ 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 11.1

If you click Show help for a selected issue in IntelliJ IDEA 11.1, an error is shown.
Workaround: Use the Documentation Wiki at http://www.klocwork.com/products/documentation/current/ to find the help for the issue.

Changes made to the Japanese Documentation after GA are only available online

The help that appears within the Klocwork tools is the version that was shipped with GA. For the latest version of our Japanese documentation, use the Documentation Wiki.
Workaround: Use the Documentation Wiki at http://www.klocwork.com/products/documentation/current-ja/ to see the latest version of the Japanese documentation.
Retrieved from "http://www.klocwork.com/products/documentation/current/Release_Notes"