ALLOC.POSTINIT : Dynamic Allocation After Initialization

Summary

A program performs dynamic allocation outside the initialization phase.

For the purpose of this check, memory allocation is considered to be in the initialization phase if it takes place in a function f() specified with configuration file parameter DYN_INIT_FUNCTIONS, or in a function directly or transitively called by f().

Properties

WARNING_FILTER += allow class="Dynamic Allocation After Initialization"

Example

#include <stdlib.h>

char * disk_buff;
char * network_buff;

/* With factory settings, function name 'dyn_init' matches a
 * DYN_INIT_FUNCTIONS rule, so this function can directly or
 * transitively call allocator functions without triggering a 'Dynamic
 * Allocation After Initialization' warning
 */
void dyn_init(void){
    disk_buff = malloc(1024);
    network_buff = malloc(2048);
}

int main(int argc, char *argv[]){
    char *r;
    char rv = 0;
    /* starting process - do all dynamic allocation now */
    dyn_init();

    /* no more dynamic allocation from this point on */
    /* ... */
    r = malloc(5);      /* 'Dynamic Allocation After Initialization' warning issued here */
    /* ... */
    if (r){
      rv = 1;
      free(r);
    }
    return rv;
}

Triggering Functions

Warnings of this class can be triggered by the following functions.

• Any function treated as an allocator by CodeSonar:
  • any library function that is recognized as an allocator because CodeSonar ships with a library model that identifies it as such, and
  • any function for which you have added a library model identifying it as an allocator.
• Any function specified with configuration file parameter ALLOCATOR_FUNCTIONS.

Notes

Only code reachable from a program entry point can trigger warnings for this class. CodeSonar will treat a function as a program entry point if it is specified with configuration file parameter PROGRAM_ENTRY_POINTS. The factory setting of this parameter instructs CodeSonar to treat main() and init() as entry points.

Relevant Configuration File Parameters

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

• ALLOCATOR_FUNCTIONS
• DFS_MAX_LOCAL_VISITED
• DFS_MAX_VISITED_COEFFICIENT
• DFS_MAX_VISITED_CONSTANT
• DYN_INIT_FUNCTIONS
• PROGRAM_ENTRY_POINTS
• REPORT_SIMILAR_WARNINGS
• WARNING_FILTER