Dossy Shiobara wrote:
There's very little memory debugging support for Tcl or AOLserver that
I'm aware of. Your options are commercial memory leak analysis tools
(Purify, etc.) or free tools (Valgrind, etc.) -- Tcl and AOLserver's
ability to introspect into "what's using memory, and how" at runtime
isn't really there.
Actually, Tcl's memory debugging capabilities are useful for some
applications, but you have to compile the support in. It is done
with --enable-symbols=mem. When used with purify, you also want
to define -DPURIFY to get single-obj (non-pooled) allocation.
There may be some conflict with the threaded mem allocator which
should be checked, but it should all work, just slower.
When compiled with memory debugging, you get the Tcl-level 'memory'
command:
http://www.tcl.tk/man/tcl8.4/TclCmd/memory.htm
Note that this only controls Tcl alloc (ckalloc or Tcl_Alloc),
which is all that Tcl itself uses. If the leak is in AOLServer
where it isn't using the Tcl alloc, that would not be detected.
--
Jeff Hobbs, The Tcl Guy
http://www.ActiveState.com/, a division of Sophos
--
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.
