When I'm writing C, I typically have structures like this: 
#ifdef DEBUG_MEM
    fprintf(memlog, "malloced(%d)\n", pointer);
#endif

#ifdef DEBUG_MEM
    fprintf(memlog, "freed(%d)\n", pointer);
#endif

[download]

Then I use perl to analyze the logfile. You can't just do it with eyeballs, because sometimes the same memory gets malloc()ed and freed a few times. Also, with XS, it's a little less explained what's happening when which macro is called... but the strategy is sound -- even if it's a small-project kind of strategy.

I also think, trying to do the demalloc in DESTROY is the wrong approach. It would be better to pull as much of the XS up into perl as possible. If you want automatic, use perl. If you want explicitly-detailed-and-micromanaged, use XS/C.

-Paul

In reply to Re: Handing Memory Leaks due to XS holding on to references by jettero
in thread Handing Memory Leaks due to XS holding on to references by kthakore

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.