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? -- Groeten, Peter What do you mean that wasn't a copy? - - Heb je een Dreambox 7000S ? - Kijk eens op http://www.dreamvcr.com - Kijk ook op http://www.lindeman.org - ICQ 22383596 - Uptime lindeman.org - 7 days, 3 hours and 28 minutes, 1 user logged in. - 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]
