Thanks for the suggestion about dumping the @results array. That did help. Well, sort of. It made me more confused, actually. In the find_thread routine, I added a line before the return:

print "find_thread dump $dir: " . Dumper(@results) . "\n";

I then run my script 10 times dumping the results to a 10 files. What I am finding is that the dump of @results can sometimes have output that is from another directory entirely. For example:

find_thread dump /vobs/doc: 
$VAR1 = '/vobs/license_manager/install/LMInstall/LM_Install.iap_xml@@/
+main/v4.0.0_gxp_patch/0';
$VAR2 = '/vobs/license_manager/install/LMInstall/LM_Install.iap_xml@@/
+main/v4.0.0_gxp_patch/1';
$VAR3 = '/vobs/license_manager/install/LMInstall/LM_Install.iap_xml@@/
+main/v4.0.0_gxp_patch/2';
$VAR4 = '/vobs/license_manager/install/LMInstall/LM_Install.iap_xml@@/
+main/v4.0.0_gxp_patch/3';
SIZE /vobs/doc: 4

find_thread dump /vobs/drs: 
$VAR1 = '/vobs/license_manager/install/LMInstall/LM_Install.iap_xml@@/
+main/v4.0.0_gxp_patch/0';
$VAR2 = '/vobs/license_manager/install/LMInstall/LM_Install.iap_xml@@/
+main/v4.0.0_gxp_patch/1';
$VAR3 = '/vobs/license_manager/install/LMInstall/LM_Install.iap_xml@@/
+main/v4.0.0_gxp_patch/2';
$VAR4 = '/vobs/license_manager/install/LMInstall/LM_Install.iap_xml@@/
+main/v4.0.0_gxp_patch/3';
SIZE /vobs/drs: 4

[download]

Which is totally confusing. @results is local to find_thread and shouldn't know anything about the other threads. What is even weirder is that when I switch to not use ClearCase find, and just find directories on the system, it seems to all work fine. So at this point, I am thinking that spawning multiple ClearCase find commands at once is causing an issue. I'll take it up with IBM.

In reply to Re^2: creating unknown number of threads and then join results by rudds_perl_habit
in thread creating unknown number of threads and then join results by rudds_perl_habit

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.