Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
Found need to execute kamailio with -dddd flag.
Now I can see messages like
0(4041924) DEBUG: <core> [core/mem/q_malloc.c:526]: qm_free(): freeing frag. 0xffff9f2fa8e0 alloc'ed from crypto/lhash/lhash.c: +0x138a34:ERR_load_strings_const+0x20:ERR_load_ENGINE_strings+0x38:+0x13a150:+0x15b474:+0xf7a4:CRYPTO_THREAD_run_once+0xc:OPENSSL_init_crypto+0x1a8:ERR_get_state+0x104:ERR_clear_error+0xc:+0x15b34c:+0xf7a4:CRYPTO_THREAD_run_once+0xc:OPENSSL_init_crypto+0x10c:+0xcfde4:+0x15b3f4:+0xf7a4:CRYPTO_THREAD_run_once+0xc:OPENSSL_init_crypto+0x298:OPENSSL_init_ssl+0x3c:tls_h_mod_pre_init_f+0xb0c:pre_init_tls+0x2c:main+0x98bc:__libc_start_main+0xdc:(225)
But allocation strings for the same fragment look like
0(4041924) DEBUG: <core> [core/mem/q_malloc.c:419]: qm_malloc(): qm_malloc(0xffff9f120000, 16832) returns address 0xffff9f2fa918 frag. 0xffff9f2fa8e0 (size=16832) on 1 -th hit
Looks like tracing print only for free operaions and not preint for alloc operations.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.