Re: [sr-dev] 3.3 presence crash

Hello, overall, it's pretty much harmless, I added the message to see eventual double free in even f_malloc. When q_malloc (memory debugger manager) is used, an abort() is executed. But now is the fast malloc (f_malloc) which didn't try to catch these situation at all, ignoring it. Maybe we should make it DBG. Ideally, the double free should be found and avoided, which will be easier to do with q_malloc on. For that you have to set MEMDBG=1 in Makefile.defs or in command line when compiling. Cheers, Daniel On 6/14/12 7:05 PM, Juha Heinanen wrote: -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio Advanced Training, Seattle, USA, Sep 23-26, 2012 - http://asipto.com/u/katu Kamailio Practical Workshop, Netherlands, Sep 10-12, 2012 - http://asipto.com/u/kpw