Virtual functions allow for static dispatch the choice of member function calls to be determined at runtime run time based on the dynamic type of the object that the member function is being called on. This convention supports object-oriented programming practices commonly associated with object inheritance and function overriding. When calling a nonvirtual member function or when using a class member access expression to denote a call, the specified function is called. Otherwise, a virtual function call is made to the final overrider in the dynamic type of the object expression.
However, during the construction and destruction of an object, the rules for virtual method dispatch on that object are restricted. The C++ Standard, [class.cdtor], paragraph 4 [ISO/IEC 14882-2014], states the following:
Member functions, including virtual functions, can be called during construction or destruction. When a virtual function is called directly or indirectly from a constructor or from a destructor, including during the construction or destruction of the class’s non-static data members, and the object to which the call applies is the object (call it
x) under construction or destruction, the function called is the final overrider in the constructor’s or destructor’s class and not one overriding it in a more-derived class. If the virtual function call uses an explicit class member access and the object expression refers to the complete object ofxor one of that object’s base class subobjects but notxor one of its base class subobjects, the behavior is undefined.
Do not directly or indirectly invoke a virtual function from a constructor or destructor that attempts to call into the object under construction or destruction. Because the order of construction starts with base classes and moves to more derived classes, attempting to call a derived class function from a base class under construction is dangerous: the . The derived class has not had the opportunity to initialize its resources, which is why calling a virtual function from a constructor does not result in a call to a function in a more derived class. Similarly, an object is destroyed in reverse order from construction, so attempting to call a function in a more derived class from a destructor may access resources that have already been released.
...
In this noncompliant code example, the base class attempts to seize and release an object's resources through calls to virtual functions from the constructor and destructor. However, it does not result in calling the B::B() constructor calls B::seize() rather than D::seize(). Likewise, the B::~B() destructor calls B::release() or rather than D::release().
| Code Block | ||||
|---|---|---|---|---|
| ||||
struct B {
B() { seize(); }
virtual ~B() { release(); }
protected:
virtual void seize();
virtual void release();
};
struct D : B {
virtual ~D() = default;
protected:
void seize() override {
B::seize();
// Get derived resources...
}
void release() override {
// Release derived resources...
B::release();
}
};
|
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
classstruct A { A() { // f(); // WRONG! A::f(); // Okay } virtual void f(); }; |
OOP50-CPP-EX2: It is permissible to call a virtual function that has the final virt-specifier from a constructor or destructor, as in this example:.
| Code Block | ||||
|---|---|---|---|---|
| ||||
classstruct A { A(); virtual void f(); }; classstruct B : public A { B() : A() { f(); // Okay } void f() override final; }; |
Similarly, it is permissible to call a virtual function from a constructor or destructor of a class that has the final class-virt-specifier, as in this example:.
| Code Block | ||||
|---|---|---|---|---|
| ||||
classstruct A { A(); virtual void f(); }; classstruct B final : public A { B() : A() { f(); // Okay } void f() override; }; |
In either case, f() must be the final overrider, guaranteeing consistent behavior of the function being called.
Risk Assessment
Rule | Severity | Likelihood |
|---|
Detectable | Repairable | Priority | Level |
|---|---|---|---|
OOP50-CPP | Low | Unlikely |
Yes | No | P2 | L3 |
Automated Detection
Tool | Version | Checker | Description |
|---|
4260, 4261, 4273, 4274,
4275, 4276, 4277, 4278,
4279, 4280, 4281, 4282
| Astrée |
| virtual-call-in-constructor invalid_function_pointer | Fully checked | ||||||
| Axivion Bauhaus Suite |
| CertC++-OOP50 | |||||||
| Clang |
| clang-analyzer-alpha.cplusplus.VirtualCall | Checked by clang-tidy | ||||||
| CodeSonar |
| LANG.STRUCT.VCALL_IN_CTOR LANG.STRUCT.VCALL_IN_DTOR | Virtual Call in Constructor Virtual Call in Destructor | ||||||
| Helix QAC |
| C++4260, C++4261, C++4273, C++4274, C++4275, C++4276, C++4277, C++4278, C++4279, C++4280, C++4281, C++4282 | |||||||
| Klocwork |
| CERT.OOP.CTOR.VIRTUAL_FUNC | |||||||
| LDRA tool suite |
| 467 S, 92 D | Fully implemented | ||||||
| Parasoft C/C++test |
| CERT_CPP-OOP50-a | Avoid calling virtual functions from constructors | ||||||
| Polyspace Bug Finder |
| CERT C++: OOP50-CPP | Checks for virtual function call from constructors and destructors (rule fully covered) | ||||||
| PVS-Studio |
| V1053 | |||||||
| RuleChecker |
| virtual-call-in-constructor | Fully checked | ||||||
| Security Reviewer - Static Reviewer |
| UNSAFE_07 | Fully implemented | ||||||
| SonarQube C/C++ Plugin |
| S1699 |
Related Vulnerabilities
Search for other vulnerabilities resulting from the violation of this rule on the CERT website.
Bibliography
| [Dewhurst |
| 2002] | Gotcha |
| #75, "Calling |
| Virtual Functions in |
| Constructors and |
| Destructors" | |
| [ISO/IEC 14882-2014] | Subclause 5.5, "Pointer-to-Member Operators" |
| [Lockheed Martin |
| 2005] | AV Rule 71.1, "A class' |
| s virtual functions shall not be invoked from its destructor or any of its constructors" |
| [Sutter |
| 2004] | Item 49, |
...
| "Avoid Calling Virtual Functions in Constructors and Destructors" |
...