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.THREAD.RUN

JD.THREAD.RUN occurs when a Thread.run() method is called explicitly.

Vulnerability and risk

In most cases, this is a mistake. The method is called implicitly by the thread itself. After a Thread.start() method has been invoked, calling Thread.run() will not start a thread.

Mitigation and prevention

Should you change it to Thread.start()?

Example 1

9      static void start() {
10         new Thread(){
11             public void run(){
12                 // do something
13             }
14         }.run();
15     }

JD.THREAD.RUN is reported for line 14: There is a call to the 'Thread.run()' method. This method is not meant to be called explicitly. Should probably be replaced with 'Thread.start()'?