ALLOC.DI : Double Initialization

JavaScript is not currently enabled, but is required for full CodeSonar manual search and browse functionality.

If you are viewing this file in your hub's Web GUI, enable JavaScript in your browser: you will also need it for GUI functionality.

If you opened this file directly from disk, your browser may be directly suppressing JavaScript functionality: certain browsers perform this suppression on local files (but not files delivered by web servers) for security reasons.

If you access the manual through the hub's Web GUI, the functionality will not be suppressed because the hub is a web server.
Alternatively, your browser may allow you to explicitly disable the security setting that suppresses functionality. See the CodeSonar FAQ for more information.

CodeSonar^® 9.2p0

CONFIDENTIAL

CodeSecure Inc

ALLOC.DI : Double Initialization

Summary

Two attempts to initialize the same dynamic object without an intervening deletion of the object.

Properties

MisraC++2023

MisraC++2023:0.3.2

A function call shall not violate the function's preconditions

CWE

CWE:675

Multiple Operations on Resource in Single-Operation Context

Triggering Functions

CodeSonar ships with library models that allow it to recognize functions such as Win32 InitializeCriticalSection() that initialize a dynamic object. If one of these functions is called to initialize a dynamic object that is definitely already initialized by an earlier call, a warning will be issued.

If you have created a custom library model for some function f() in terms of one of these existing models, calls to f() will also be capable of triggering Double Initialization warnings.

Example

#include <windows.h>

void double_init(void){
    CRITICAL_SECTION cs;
    /* ... */
    InitializeCriticalSection(&cs);
    DeleteCriticalSection(&cs);
    InitializeCriticalSection(&cs);  /* ok because of intervening DeleteCriticalSection() */
    InitializeCriticalSection(&cs);  /* warning issued here */
    DeleteCriticalSection(&cs);
}

Relevant Configuration File Parameters

The following configuration file parameters affect checks for this warning class.