2 Oct
2012
2 Oct
'12
7:22 p.m.
Quite strange I would say.
No, debug parameter value does not replace warning level with debug -
just to comment on your previous message related to it.
But now do you get the messages related to alloc and free operations?
It should be first the message from mem/q_malloc.c, line 437, after it
is the condition on free(0).
Cheers,
Daniel
On 10/2/12 6:04 PM, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
--
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
You have to set memdbg (or memlog) parameters to
lower value than
debug.
now i have
memdbg=1
memlog=1
debug=2
and when i stop sip-proxy i still don't get any free(0) warnings. i do
get the warnings if i have not set memdbg and memlog.
-- juha