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

Types of Java Path checkers

You can create three types of Java Path checkers:

  • Security Vulnerability (SV)checkers detect tainted strings, their concatenation, and other types of tainted data.
  • Resource Leak (RLK) checkers locate the resource and detect the ways in which the resource can be lost. RLK (Resource Leak) issues are reported when some resources were allocated and not properly disposed after use. Failing to properly dispose a resource can lead to such problems as:
    • too many files being open
    • an application not being able to access a temporary file when it is needed
    Note: When creating RLK checkers, you only need to identify the source(s) and not the sink. The sink is the point at which the resource is lost.
  • Commoncheckers track data from the time it appears in the code execution to when it is used by the program.