2 Oct
2012
2 Oct
'12
3:18 p.m.
Daniel-Constantin Mierla writes:
But now do you get the messages related to alloc and
free operations?
yes.
It should be first the message from mem/q_malloc.c, line 437, after it
is the condition on free(0).
i see lots of these kind of entries, but no free(0) entries:
Oct 2 21:56:02 siika /usr/sbin/sip-proxy[15833]: NOTICE: <core>
[mem/q_malloc.c:437]: qm_free(0x7f31b9db0000, 0x7f31ba93a4b0), called from <core>:
usr_avp.c: destroy_avp_list_unsafe(634)
Oct 2 21:56:02 siika /usr/sbin/sip-proxy[15833]: NOTICE: <core>
[mem/q_malloc.c:468]: qm_free: freeing frag. 0x7f31ba93a480 alloc'ed from
<core>: usr_avp.c: create_avp(187)
...
Oct 2 21:56:06 siika /usr/sbin/sip-proxy[15847]:
NOTICE: <core> [mem/q_malloc.c:437]: qm_free(0x7f31c0c19010, 0x7f31c0d284f8), called
from nathelper: nathelper.c: nh_timer(1986)
Oct 2 21:56:06 siika
/usr/sbin/sip-proxy[15847]: NOTICE: <core> [mem/q_malloc.c:468]: qm_free: freeing
frag. 0x7f31c0d284c8 alloc'ed from nathelper: nathelper.c: nh_timer(1871)
free(0) at close shows up only when i have not set memdbg/memlog vars.
-- juha