Hello all. I am running a very lengthy code (too lengthy to upload, and may be proprietary). I am getting these warnings: 
        eval {...} called at /edata/eng/ldagan/voodoo_from_1.1.7.b4/bi
+n/../DesignLibs/ScriptLib/Generic/WMPerl/voodoo/voodooThreads.pm line
+ 73 thread 3
Use of uninitialized value $_ in pattern match (m//) at (eval 60) line
+ 1, <$SIM_F> line 50.
Use of uninitialized value $_ in pattern match (m//) at (eval 61) line
+ 1, <$SIM_F> line 50.

[download]
I have tried to look, but could not find any pattern match that uses $_ in the file. I could be missing something, of course. Line 73 is: 
$thread = threads->create(\&executeSimThread, $tb, $i, "Thread data " 
+. $i, $all_shary_for_subs, $global_non_share_ref  );

[download]
I could not find in the subroutine any usage of $_ in pattern matching. Thanks.

In reply to mapping warning from an eval code to actual line in text by ISAI student

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.