freebsd-ports/devel/p5-Test-LeakTrace/pkg-plist

%%SITE_PERL%%/%%PERL_ARCH%%/Test/LeakTrace.pm
%%SITE_PERL%%/%%PERL_ARCH%%/Test/LeakTrace/JA.pod
%%SITE_PERL%%/%%PERL_ARCH%%/Test/LeakTrace/Script.pm
%%SITE_PERL%%/%%PERL_ARCH%%/auto/Test/LeakTrace/.packlist
%%SITE_PERL%%/%%PERL_ARCH%%/auto/Test/LeakTrace/LeakTrace.bs
%%SITE_PERL%%/%%PERL_ARCH%%/auto/Test/LeakTrace/LeakTrace.so
@dirrm %%SITE_PERL%%/%%PERL_ARCH%%/auto/Test/LeakTrace
@dirrmtry %%SITE_PERL%%/%%PERL_ARCH%%/auto/Test
@dirrm %%SITE_PERL%%/%%PERL_ARCH%%/Test/LeakTrace
@dirrmtry %%SITE_PERL%%/%%PERL_ARCH%%/Test
- Add p5-Test-LeakTrace 0.13 Test::LeakTrace provides several functions that trace memory leaks. This module scans arenas, the memory allocation system, so it can detect any leaked SVs in given blocks. Leaked SVs are SVs which are not released after the end of the scope they have been created. These SVs include global variables and internal caches. For example, if you call a method in a tracing block, perl might prepare a cache for the method. Thus, to trace true leaks, no_leaks_ok() and leaks_cmp_ok() executes a block more than once. WWW: http://search.cpan.org/dist/Test-LeakTrace/ 2011-08-10 14:13:56 +02:00			`%%SITE_PERL%%/%%PERL_ARCH%%/Test/LeakTrace.pm`
			`%%SITE_PERL%%/%%PERL_ARCH%%/Test/LeakTrace/JA.pod`
			`%%SITE_PERL%%/%%PERL_ARCH%%/Test/LeakTrace/Script.pm`
			`%%SITE_PERL%%/%%PERL_ARCH%%/auto/Test/LeakTrace/.packlist`
			`%%SITE_PERL%%/%%PERL_ARCH%%/auto/Test/LeakTrace/LeakTrace.bs`
			`%%SITE_PERL%%/%%PERL_ARCH%%/auto/Test/LeakTrace/LeakTrace.so`
			`@dirrm %%SITE_PERL%%/%%PERL_ARCH%%/auto/Test/LeakTrace`
			`@dirrmtry %%SITE_PERL%%/%%PERL_ARCH%%/auto/Test`
			`@dirrm %%SITE_PERL%%/%%PERL_ARCH%%/Test/LeakTrace`
			`@dirrmtry %%SITE_PERL%%/%%PERL_ARCH%%/Test`