valgrind can do this and a lot more. I recommend that, at least in Linux.
boris@foo:~> valgrind perl ~/xxx.pl ==28372== Memcheck, a.k.a. Valgrind, a memory error detector for x86-l +inux. ==28372== Copyright (C) 2002, and GNU GPL'd, by Julian Seward. ==28372== Using valgrind-1.9.6, a program instrumentation system for x +86-linux. ==28372== Copyright (C) 2000-2002, and GNU GPL'd, by Julian Seward. ==28372== Estimated CPU clock rate is 1005 MHz ==28372== For more details, rerun with: -v ==28372== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 90 from + 2) ==28372== malloc/free: in use at exit: 600146 bytes in 13063 blocks. ==28372== malloc/free: 21262 allocs, 8199 frees, 1013245 bytes allocat +ed. ==28372== For a detailed leak analysis, rerun with: --leak-check=yes ==28372== For counts of detected errors, rerun with: -v
Boris

In reply to Re: memory profiling by borisz
in thread memory profiling by bronto

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.