Stuart Freedman <stuart@...> wrote: > One thing I noticed yesterday was that it appeared that mxsync > sessions got disconnected & reconnected a lot. Is this supposed to > happen? Could there be an issue related to not freeing resources > before re-initiating such connections? Should I try to get a core > dump/stack trace? You can enhance the debug message you get when malloc fails. Make a sweep change, adding something such as: "%s:%d malloc falied: %s", __FILE__, __LINE__, strerror(errno) That way you'll see if the problem happen at the same place or not. Next step is to display the size requested by malloc to see if there is a miscalculation somewhere. -- Emmanuel Dreyfus http://hcpnet.free.fr/pubz manu@...
Message
Re: [milter-greylist] Re: Frequent 4.0b1 crashes on FreeBSD
2007-08-28 by manu@netbsd.org