On Tue, Aug 10, 2004 at 10:19:32AM +0200, Zoran Vasiljevic wrote: > You might want to distinguish between real leaks and pure memory > consumption. Purify will report real leaks, that is, if you allocate
Well, yes. But my problem is that my memory consumption is buggy, and I haven't been able to figure out why. Any suggestions on how I could track this down? I thought perhaps Tcl's "memory trace on" could help give me an idea of why/when the memory is being allocated, so I built Tcl with --disable-shared, "MEM_DEBUG_FLAGS = -DTCL_MEM_DEBUG", and -DUSE_THREAD_ALLOC=0. With that, when I run tclsh8.4 the memory trace command works just fine, but from AOLserver it errors out with 'invalid command name "memory"'. So it seems that for some reason the memory command just plain doesn't work in AOLserver, even if you link it to a Tcl where the memory command does work. Anybody know why? Is this normal? > In Tcl, the most common error is bad handling of refcounts of Tcl > objects. I'm not and never have been doing any refcounting of Tcl objects at all, so that can't be it. (Actually, my C code is using the old-style string based Tcl APIs only, no Tcl objects.) -- 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.
