26 Apr
2021
26 Apr
'21
10:08 a.m.
On 26.04.21 15:33, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
That is the log when the DBG_QM_MALLOC is not defined.
By default DBG_QM_MALLOC should be defined by having MEMDBG=1 in
src/Makefile.defs.
To not define it, maybe you set MEMDBG=0 for 'make cfg ...' command or
somewhere in the debian specs.
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - Online
May 17-20, 2021 (Europe Timezone) - June 7-10, 2021 (America Timezone)
* https://www.asipto.com/sw/kamailio-advanced-training-online/
On 26.04.21 11:02, Juha Heinanen wrote:
I'm not sure how to compile with DBG_QM_MALLOC. I added
to debian rules'
configure command parameter
$(MAKE) cgf DBG_QM_MALLOC=1 ...
and after that I didn't notice changes in syslog output. Again lots of these:
Apr 26 16:29:49 edge /usr/bin/edge-proxy[7620]: INFO: <core>
[core/mem/q_malloc.c:529]: qm_free(): freeing a free fragment
(0x7f1840b5c460/0x7f1840b5c470) - ignore Daniel-Constantin Mierla writes:
Can you compile
with DBG_QM_MALLOC, then reproduce and send a few of
those log messages? Is your kamailio compiled without defining
DBG_QM_MALLOC (which should
be on by default)
Yes, I have not defined DBG_QM_MALLOC.