[SR-Users] WARNING:fm_free at stop

[Daniel-Constantin Mierla]

Strange, unless it is related to mem debug logs.

Anyhow, I pushed a patch to master branch to print the file and line for 
free(0) when compiled with memdbg=1.

Try it to see if you get the details of free(0) location.

Cheers,
Daniel

On 10/2/12 9:18 PM, Juha Heinanen wrote:
> 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

-- 
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Berlin, Nov 5-8, 2012 - http://asipto.com/u/kat
Kamailio Advanced Training, Miami, USA, Nov 12-14, 2012 - http://asipto.com/u/katu