Thanks for the reply beauregard.

You are right, this was one of the major sources of crashes - however, I'm still left with that crash on a malloc in the C thread.

I've done a little more digging, and I'm wondering if it's because there is no Perl interpreter built in that C thread. If the standard Perl headers are used, then malloc gets redefined to use perl pointers associated with the thread - and since perl hasn't been set up: Boom! If this is the case, how do I get around that? I'm assuming it should be just a case of using the OS malloc/free for all memory management, then it shouldn't matter if a Perl interpreter has been built or not?

Thanks.

In reply to Re^2: General memory management for embedded/extended perl with C threads by Anonymous Monk
in thread 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.