(MeowChow) Re: Looking for Leaks

Replies are listed 'Best First'.
Re: (MeowChow) Re: Looking for Leaks by dragonchild (Archbishop) on Aug 09, 2001 at 23:26 UTC
Well, isn't there a way/tool to, from the main section of the script, find out which memory locations aren't accessible? Everything should be accessible (except for closures) and all of that can be pointed out. You can then read through the output, mark off which you know to be closures, and then you have your answer... ------ /me wants to be the brightest bulb in the chandelier! Vote paco for President!	[reply]
Re: Re: (MeowChow) Re: Looking for Leaks by bikeNomad (Priest) on Aug 09, 2001 at 23:44 UTC
If things weren't accessible, how would you find them? At least in pure Perl, this would be impossible. You could iterate over all the symbol tables, following references to reachable objects, but this wouldn't find things that had leaked.	[reply]
Re: Re: Re: (MeowChow) Re: Looking for Leaks by dragonchild (Archbishop) on Aug 09, 2001 at 23:49 UTC
In pure Perl, yes. In XS, it should be possible to iterate through the entire region of memory and see if anything has a valid reference. Also (and I'm stretching my memory here), isn't there a way in C to find out all the malloc'ed areas? You could compare that with the list of all reachable objects and see if there's a discrepancy... ------ /me wants to be the brightest bulb in the chandelier! Vote paco for President!	[reply]


The stupid question is the question not asked
	PerlMonks