I’m building a cross platform xs module that creates a few C threads when the module is initialised. The lowest comment denominator is win32, pthreads and perl 5.6.1 (Activestate build 638).

The application is pretty much working, although I am getting a repeatable crash in one of my C threads when malloc is called.

After a lot of hunting and debugging I "solved" a lot of the problems by making sure the C and XS code use the same memory allocation calls (XSUB.h was refining malloc to PerlMem_malloc). Then I followed the various perl header files, and got very lost…:)

The end result is that I’m confused to what malloc functions I should be using in my C threads? I’ve searched the web and the manuals, but I just can’t see – what I assume is a simple solution?

Thanks.

In reply to General memory management for embedded/extended perl with C threads by Anonymous Monk

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.