On Mon, 31 May 2004, Peter Lindeman wrote: > Davide Libenzi wrote: > > > 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. > > When will XMail creates the XMail.memleaks file? It is running here now > but the file is not created yet. Will it be created only when a leak is > detected?
Only when it exits. - 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]
