I saw your response below. I don't know anything about perl internals or embedding, but I know a little about threads. And I know generally perl is not "thread safe". If you're initializing something regarding perl in your main thread, then using it in the child threads, this is likely a bad idea. Also the sharing of anything among child threads or with the main thread should occur well outside the purvue of anything touching the embedded perl bits. If you keep things isolated in each thread, I don't see why you can't have isolated perl instances embedded there and using shared variables (outside of perl) to communicate (again outside of perl). But it'd get complicated quickly.

In reply to Re: Crash at perl_parse() function by perlfan
in thread Crash at perl_parse() function by prabakar.bhatt

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.