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

JD.CALL.WRONGSTATIC

JD.CALL.WRONGSTATIC appears when a static method is called by means of instance reference.

Vulnerability and risk

Calling of a static method by means of an instance reference is a bad coding practice, and it can cause incorrect behavior. For example, if static method interrupted() is called by means of an instance reference, then the returned state would be the state of the current Thread, not the state of the given instance. If you wants to get the state of the instance, use a non-static call isInterrupted().

Mitigation and prevention

Do not call static methods by means of instance references.

Example 1

9      void run(final Thread thread) throws Throwable{
10         thread.interrupted();
11     }

JD.CALL.WRONGSTATIC is reported for line 10: Call to static method 'java.lang.Thread.interrupted' via instance reference.