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:
after pua bug fix was commited to 3.3 branch, i get this kind of message
to syslog related to pua publish/notify that don't remember seeing ever before
and that looks very dangerous:
Jun 14 20:02:52 siika /usr/sbin/pres-serv[4339]: INFO: <core>
[mem/f_malloc.c:529]: freeing a free fragment (0x7f5da71031a0/0x7f5da71031b0) - ignore
-- juha
--
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
_______________________________________________
sr-dev mailing list
[email protected]
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
