maria-developers team mailing list archive

["Vladislav Vaintroub" <wlad@xxxxxxxxxxxxxxxx>]

There is a bunch of "Freeing NULL pointer at line 405, 'comp_err.c'"
messages in the build log.
My wild guess was safemalloc, and indeed, a  merge from 5.1-feedbqack
(re)introduced unconditional -DSAFEMALLOC in debug builds. I removed it
again now from 5.1-5.2-5.3, and it builds fine.  I presume safemalloc builds
if we do any at  would have this problem. Why freeing NULL  pointer is bad I
do not know, in C standard library it is ok.



> -----Original Message-----
> From: Sergei Petrunia [mailto:psergey@xxxxxxxxxxxx]
> Sent: Dienstag, 11. Oktober 2011 19:42
> To: Sergei Golubchik
> Cc: maria-developers@xxxxxxxxxxxxxxxxxxx; wlad@xxxxxxxxxxxxxxxx
> Subject: Your push broke windows builds on 5.3
> 
> Hi Serg,
> 
> Your latest push into 5.3 broke compilation on Windows:
> 
> http://buildbot.askmonty.org/buildbot/builders/win2008r2-vs2010-i386-
> packages/builds/273/steps/build_zip/logs/stdio
> 
> http://buildbot.askmonty.org/buildbot/builders/win32-
> debug2/builds/734/steps/build/logs/stdio
> 
> Could you please fix it? (If you don't have any idea what could be the
cause,
> maybe Wlad could help us?)
> 
> BR
>  Sergey
> --
> Sergei Petrunia, Software Developer
> Monty Program AB, http://askmonty.org
> Blog: http://s.petrunia.net/blog