Hi, Vladislav! On Oct 11, Vladislav Vaintroub wrote: > 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.
I've fixed comp_err.c too. Regards, Sergei _______________________________________________ Mailing list: https://launchpad.net/~maria-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~maria-developers More help : https://help.launchpad.net/ListHelp
