I setup an XMail leak tracing infrastructure for Linux. I was hoping that valgrind was doing the job fine, but it turned out not to be the case. The thing lives as an external patch:
http://www.xmailserver.org/xmail-memtracer-0.1.diff You get the patch and the XMail .tar.gz, and: $ tar xvzf xmail-?.??.tar.gz $ cd xmail-?.?? $ patch -p1 < ../xmail-memtracer-0.1.diff $ export XMAIL_DEBUG=1 $ make -f Makefile.lnx Then you copy the XMail binary from inside the "bin" directory to your XMail's binary folder, and you restart XMail. To get clean memory leak reports, XMail must be shutdown cleanly: $ touch $MAIL_ROOT/.shutdown Then you have to wait (ps) that the last XMail process vanished, and the report will be available in /tmp/XMail.memleaks. You need to send the report to me together with the *exact* copy of the binary that generated the report. Note that XMail uses a little bit more memory when traced, but nothing close to the amount that valgrind uses. I am running it by 24 hours, and I can say that it has zero leaks here. - Davide - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
