> I guess someone could incrementally try each developement snapshot to > between 3.0 and 4.0 alpha to see when things went wrong. But > that's not > a funny job. :-/ > > The other option is to use specialized tools for tracking down memory > leaks. Any specialist here? Someone that could perform a > Coverity run on > the sources? > Hello, The attached patch may give a bit more of information about the session in which the error may occur. Bests, Attila
Message
RE: [milter-greylist] version 4.0a4 aborts with message: "mg_setreply(): invoked twice"
2007-05-30 by attila.bruncsak@itu.int