Hi monks,

I've written a fair ammount of perl over the years but now I'm working on a script that needs to run for a week or so. I'm just starting to get to grips with the debugger. My script is consuming large amounts of memory, enough that it will only run for a few hours. Everything is strict;
Devel:leak is showing me things like:

old (0): 0 old (0): 0 old (0): 0 new 0248BF0C : new 0248BFC0 :
What on earth does that mean? How do I use it to track down the problem? Is this a red herring? Is there anything missing that compiling with -DDEBUGGING would add? If so am I stuffed, I'm using Activestate on WinXP? I can't move to a different platform because of the applications that perl is talking to.

Alternatively can you give me any pointers to good guides that will walk me through debugging memory problems from beginner to advanced?

Cheers
nonk


In reply to understanding devel::leak by nonnonymousnonk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.