5 Feb
2014
5 Feb
'14
10:08 a.m.
On 05/02/14 08:57, Øyvind Kolbu wrote:
Indeed, I checked 4.1, MEMDBG is set for the branch. You can set in config:
mem_safety=1
Cheers,
Daniel
--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
-----Original
Message-----
From: Daniel-Constantin Mierla
Sent: Tuesday, February 04, 2014 9:26 PM
Hello,
this happens due to an abort() that is executed only when MEMDBG is set
(memory debugging is turned on). It's main purpose is to spot double frees.
For production, either MEMDBG is not set or you set mem_safety global
parameter. You will get the log message, but the application keeps running.
I also recommend to upgrade to 4.1.1, there were some fixes that affect this
case as well.
On the other side, I will try to see what could be the situation to end in the
two frees once I get a chance (still in the middle of a traveling period for a
while here).
OK, will try a git after 4.1.1. I'm keeping the core file if you
want it or a full backtrace.
Both MEMDBG and mem_safety are default. Neither config nor build changes them.