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

UNINIT.CTOR.MIGHT

Uninitialized variable in constructor possible

The UNINIT.CTOR.MIGHT checker finds class variables that may not have been initialized in the constructor.

Vulnerability and risk

In C++, primitive data type variables need to be initialized explicitly. Use of uninitialized members in class methods typically leads to unpredictable behavior, and may have security implications.

Mitigation and prevention

To avoid use of uninitialized variables, make sure that constructors initialize all class fields.

Vulnerable code example

1  class C {
2      int i;

3    public:
4      C(bool flag) {
5        if (flag) i = 0;
6      }
7  };

Klocwork flags line 6, indicating that the value of 'this->i' variable might remain uninitialized when constructor exits.