On Wed, Aug 11, 2004 at 09:26:20AM +0200, Zoran Vasiljevic wrote: > When you launch the AOLserver in foreground, run couple of requests > and then ctrl-c it, purify should report all memory that has been > allocated and not freed. The list may be long, since AS does not > make a very clean shutdown memory-wise, but you may spot your "leaks" > among those. Have you tried that?
Aha, now I am definitely getting more useful results from Purify. (Perhaps building Tcl without the '-DUSE_THREAD_ALLOC=1' as Elizabeth suggested made the difference, or maybe I was simply driving Purify incorrectly before.) When AOLserver shuts down, it spits out an ENORMOUS list of "leaked" and "potentially leaked" bytes. There appears to be a definite problem with false positive leaks here... What sort of changes to AOLserver would it take to make those go away? Would doing so be impractical? Interestingly, my total number of "potentially leaked" bytes grows with the number of requests, while the "leaked" bytes total does not. Since my memory wastage is nearly perfectly linear with number of requests, clearly if Purify is showing my bug at all, it must be hiding in the "potentially leaked" bin somewhere. (Now to track it down.) -- Andrew Piskorski <[EMAIL PROTECTED]> http://www.piskorski.com/ -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
