mirror of
https://github.com/asterisk/asterisk.git
synced 2025-10-31 10:47:18 +00:00
1a36a452bd
The pool cache gets in the way of finding use after free errors of memory pool contents. Tools like valgrind and MALLOC_DEBUG don't know when a pool is released because it gets put into the cache instead of being freed. * Added the "cache_pools" option to pjproject.conf. Disabling the option helps track down pool content mismanagement when using valgrind or MALLOC_DEBUG. The cache gets in the way of determining if the pool contents are used after free and who freed it. To disable the pool caching simply disable the cache_pools option in pjproject.conf and restart Asterisk. Sample pjproject.conf setting: [startup] cache_pools=no * Made current users of the caching pool factory initialization and destruction calls call common routines to create and destroy cached pools. ASTERISK-27704 Change-Id: I64d5befbaeed2532f93aa027a51eb52347d2b828
57 lines
2.6 KiB
Plaintext
57 lines
2.6 KiB
Plaintext
; Common pjproject options
|
|
;
|
|
|
|
;[startup]
|
|
; NOTES: The name of this section in the pjproject.conf configuration file must
|
|
; remain startup or the configuration will not be applied.
|
|
;
|
|
;cache_pools = yes ; Cache pjproject memory pools for performance
|
|
; Disable this option to help track down pool content
|
|
; mismanagement when using valgrind or MALLOC_DEBUG.
|
|
; The cache gets in the way of determining if the
|
|
; pool contents are used after being freed and who
|
|
; freed it.
|
|
; Default yes
|
|
;log_level=default ; Initial maximum pjproject logging level to log
|
|
; Valid values are: 0-6, and default
|
|
;
|
|
; Note: This option is needed very early in the startup
|
|
; process so it can only be read from config files because
|
|
; the modules for other methods have not been loaded yet.
|
|
;type= ; Must be of type startup (default: "")
|
|
|
|
;========================LOG_MAPPINGS SECTION OPTIONS===============================
|
|
;[log_mappings]
|
|
; SYNOPSIS: Provides pjproject to Asterisk log level mappings.
|
|
; NOTES: The name of this section in the pjproject.conf configuration file must
|
|
; remain log_mappings or the configuration will not be applied.
|
|
; The defaults mentioned below only apply if this file or the 'log_mappings'
|
|
; object can't be found. If the object is found, there are no defaults. If
|
|
; you don't specify an entry, nothing will be logged for that level.
|
|
;
|
|
; These logging level meanings are typically used by pjproject:
|
|
; - 0: fatal error
|
|
; - 1: error
|
|
; - 2: warning
|
|
; - 3: info
|
|
; - 4: debug
|
|
; - 5: trace
|
|
; - 6: more detailed trace
|
|
;
|
|
;asterisk_error = ; A comma separated list of pjproject log levels to map to
|
|
; Asterisk errors.
|
|
; (default: "0,1")
|
|
;asterisk_warning = ; A comma separated list of pjproject log levels to map to
|
|
; Asterisk warnings.
|
|
; (default: "2")
|
|
;asterisk_notice = ; A comma separated list of pjproject log levels to map to
|
|
; Asterisk notices.
|
|
; (default: "")
|
|
;asterisk_verbose = ; A comma separated list of pjproject log levels to map to
|
|
; Asterisk verbose.
|
|
; (default: "")
|
|
;asterisk_debug = ; A comma separated list of pjproject log levels to map to
|
|
; Asterisk debug
|
|
; (default: "3,4,5,6")
|
|
;type= ; Must be of type log_mappings (default: "")
|