I'll check on strict and warnings -- I think they're on. The code is complicated, but I posted the main loop at http://www.perlmonks.org/index.pl?node_id=217848

I did find one bug and corrected it this way:

    while($buf=~/(.*\n)/g) {
     print DEBUG  "doing <$1>\n";
     ${$Con{$fh}}{getline}($fh,$1);
     last unless $Con{$fh};  # it's possible that the connection can b
+e deleted while there's still something in the buffer
    }
    if($Con{$fh}) {
     ($this->{_})=$buf=~/([^\n\r]*)$/s;
     if(length($this->{_}) > 10000) {
      ${$Con{$fh}}{getline}($fh,$this->{_});
      ($this->{_})='';
     }
    }

[download]
The problem was that the connection was closed while there was still a line in the buffer. The if($Con{$fh}) tests for that condition.

john

In reply to Re: Re: Mysterious script crash in win2k and ActivePerl by jhanna
in thread Mysterious script crash in win2k and ActivePerl by jhanna

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.