Do not worry about it not being your "real" code, as long as the issue still occurs.

Replicating the issue in a separate environment and distilling the code down to the minimum required to show the issue is an excellent way to debug. Bugs often become obvious once you have shoveled most of the dirt out of the way.


Unfortunately I don't know too much about ithreads, so one of the more veteran monks will have to step in to help with the details.

One thing I do know is that the error message will be "thread failed to start: blah blah blah", but what it probably means is "thread failed to end cleanly. The thread could have been running for quite some time before it dies and prints such a message.

In reply to Re: ithreads not behaving as expected by SuicideJunkie
in thread ithreads not behaving as expected by madorb

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.