|Do you know where your variables are?|
Re: Tools effective in finding memory leaks in perl code.by BrowserUk (Pope)
|on Apr 26, 2013 at 19:35 UTC||Need Help??|
valgrind operates at the C/assembler level and its output is very difficult to relate back to Perl code. It is only really useful for debugging Perl's internals.
In general, the easiest way to track down leaks caused by user Perl code is to find a reliable set of inputs that demonstrate that leak and then comment out blocks of code until the leak goes away; then put the commented out bits back in smaller pieces until the leak reappears. It is usually fairly easy to find the Perl source code responsible this way.
(Of course, if the source of your leak is genuinely a Perl bug then you may need to resort to valgrind or similar to find the actual bug, but that is usually done by the p5p guys once you've demonstrated that your perl is not at fault.)
With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.