I would suspect a timing issue - when in 'production' mode, occassionally the timing of things causes a failure - a slightly delayed socket connection, a signal that gets delayed etc. When in debug mode, with everything running slower, the critical points for this behaviour get spread out and are no longer an issue.
I'd try getting better feedback from your script, in production mode, when the failure occurs, using Data::Dumper, Carp etc to report verbosely about your code's state. If you can't provoke the error at will, you need to get as much info as possible when it does happen.
Also, trap and test the return code of everything - and I mean everything.
Try writing your own signal handlers too, if that seems appropriate - stuff like
$SIG{'INT'} = &int_handler;
sub int_handler {
...verbose state printing here...
}
+++++++++++++++++
#!/usr/bin/perl
use warnings;use strict;use brain;
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.