Ignore:
Timestamp:
Jun 1, 2007 7:26:21 AM (14 years ago)
Author:
bennylp
Message:

Implement ticket #314: Added PJ_SAFE_POOL configuration in PJLIB to track down memory corruptions

File:
1 edited

Legend:

Unmodified
Added
Removed
  • pjproject/trunk/pjlib/include/pj/config.h

    r1246 r1333  
    389389 
    390390/** 
     391 * Set this flag to non-zero to enable various checking for pool 
     392 * operations. When this flag is set, assertion must be enabled 
     393 * in the application. 
     394 * 
     395 * This will slow down pool creation and destruction and will add 
     396 * few bytes of overhead, so application would normally want to  
     397 * disable this feature on release build. 
     398 * 
     399 * Default: 0 
     400 */ 
     401#ifndef PJ_SAFE_POOL 
     402#   define PJ_SAFE_POOL             0 
     403#endif 
     404 
     405 
     406/** 
    391407 * If pool debugging is used, then each memory allocation from the pool 
    392408 * will call malloc(), and pool will release all memory chunks when it 
Note: See TracChangeset for help on using the changeset viewer.