Re: [MacPerl] Memory problems in OO context

[Chris Nandor <pudge@pobox.com>]

At 11.18 -0600 1999.12.06, Matthew Langford wrote:
>The presence of leaks in various modules, or the suspicion that there are
>leaks but no proof, reinforces the point that Perl or at least MacPerl
>needs (some|more) leak-proofing tools.  And as I've said, this is ironic
>given Perl's garbage collecting.  Not as ironic as Java, which has made
>much ado over the garbage collection issue, but still ironic.
>
>I'm looking for tools to help me in this search.  It sounds like MacsBug
>may be the best shot right now.

I have two MacPerl builds here you might want.  One has -d LEAKTEST
enabled, one has -d MALLOC_LOG enabled.  Both have -D DEBUGGING enabled (as
does the version I have in my CPAN directory).  I forget how to use the
LEAKTEST one offhand.  The MALLOC_LOG one can fill up your hard drive right
quick if you leave it running.

I just put them up with the other stuff at:

    http://pudge.net/files/macperl/cpan/binaries/

-- 
Chris Nandor          mailto:pudge@pobox.com         http://pudge.net/
%PGPKey = ('B76E72AD', [1024, '0824090B CE73CA10  1FF77F13 8180B6B6'])

# ===== Want to unsubscribe from this list?
# ===== Send mail with body "unsubscribe" to macperl-request@macperl.org