----- Original Message ----- From: "Sandhu, Suchindra" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Saturday, November 26, 2005 3:03 AM Subject: Detecting memory leaks in perl scripts
> Greetings, > > Is there a known tool(preferably free/open source) to identify memory > leaks in perl scripts ? > Devel::Leak will detect when you have a leakage with perl data types - say because an xsub returns non-mortalised SV's. But there are other ways that memory leaks can arise - that Devel::Leak doesn't detect. I just usually run suspect code and watch the memory usage in TaskManager. (You can probably do the same thing programmatically using Win32::PerfLib or Win32::Process::Info ... not sure.) But, of course, none of that is guaranteed to positively identify the exact trouble spot - for which you'll need a C memory debugger. On linux, you can use valgrind or dmalloc, but I don't know what there is for Win32. I expect that Microsoft's Visual Studio has some such tool - but that's unlikely to be free. And I don't know if MinGW's 'gdb' debugger (which is free/open source) has the capability. Do you have some perl code that you believe is leaking ? If you can post some (minimal) code that you believe is leaking, then maybe we can help further. Cheers, Rob _______________________________________________ Perl-Win32-Users mailing list [email protected] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
