SIGKILL

[gaf at blu.org (Jerry Feldman)]

On Wed, 22 Jan 2003 21:08:47 -0500 (EST)
"James R. Van Zandt" <jrv at vanzandt.mv.com> wrote:

> >ftp://ftp.perens.com/pub/ElectricFence/
> 
> I second this suggestion.  It uses the microprocessor's own virtual
> memory hardware to track memory usage, so it can be much faster than
> pure software malloc() debuggers.
Just to add one comment on Purify. (Note that Purify Plus contains
Purify, PureCov and Quantify).
Purify instruments the entire executable by catching all loads and
stores and all system calls. It also intercepts all calls to malloc,
free et. al. as well as mmap(), so it is much more extensive than other
tools, but you pay for that. Tat said, Purify has a number of APIs
available to the programmer, such as a way to periodically display the
summary messages. So, you can determine at what point in your program
that a leak or potential leak occured. 

(also, Purify tracks file descriptor usage). 

-- 
Jerry Feldman <gaf at blu.org>
Boston Linux and Unix user group
http://www.blu.org PGP key id:C5061EA9
PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.blu.org/pipermail/discuss/attachments/20030123/5fb1886f/attachment.sig>