Elizabeth Thomas wrote on 8/11/04, 10:06 AM: > You can do a sanity check to see if your aolserver is using the thread > memory allocator by issuing an 'ns_info pools' command. If it returns > anything, its still on. If you are still using the pools that could > explain why Purify isn't telling you much.
Correction: ns_info pools will probably return nothing if you've done the static build (as I believe you were doing in order to use purify) as the code won't call Tcl_GetMemoryInfo in that case either. However - that doesn't mean the pools aren't there. You'll know they are if you see calls to GetBlocks in any call traces. You may have to attach a debugger to find out for sure. If the globals firstCachePtr or sharedPtr are there that means tcl was built with the thread memory allocator. -E -- 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.
