Return-Path: Delivered-To: apmail-perl-dev-archive@perl.apache.org Received: (qmail 47372 invoked by uid 500); 27 Apr 2001 01:57:44 -0000 Mailing-List: contact dev-help@perl.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Delivered-To: mailing list dev@perl.apache.org Received: (qmail 47358 invoked from network); 27 Apr 2001 01:57:44 -0000 X-Authentication-Warning: mako.covalent.net: dougm owned process doing -bs Date: Thu, 26 Apr 2001 18:55:22 -0700 (PDT) From: Doug MacEachern To: Matt Sergeant cc: dev@perl.apache.org Subject: Re: Locating leaked scalars In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N On Thu, 26 Apr 2001, Matt Sergeant wrote: > Doug, > > I found a post from you to Mosely a while back saying you'd tell him how > to track down scalar leaks, but I can't find any follow up. Is there a > way to do this that you know of, or is it a matter of firing up purify > (which I don't have, but I hear there's a GNU version) or something? url for that post? there's no single way to track down a scalar leak. if you give me an idea of whats going on, i might be able to offer a suggestion for your particular case. i have had success using purify, which requires Perl to be compiled with -DPURIFY, similar with insure++ (another commercial tool). i've never had success with any of the opensource tools. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org For additional commands, e-mail: dev-help@perl.apache.org