Two words: Log everything.

Since you can't reproduce the error and see what's happening, you have to keep looking at all times in order to be there when the bug strikes; you need a ridiculously detailed debug log file.

You can probably afford to delete it at regular intervals when things go right, because it's bound to grow fast. gzipping it works as well. A cron entry might be good for this.

You don't want to/can't delete an opened file, so open, print, close at each log entry to prevent perl from locking it.

Just make sure you can log this much without affecting efficiency before you deploy :)


/J

PS. Log files are a Good Thing. Consider using a general logging strategy to keep track of what the program does.

In reply to Re: debugging strategy? by jplindstrom
in thread debugging strategy? by mbr

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.