It sounds like this script is deployed and running regularly.

What if you add a trace log so that the next time it runs, you can follow the flow of execution and see the data as it goes?
Simply write a little function called debug_trace, that will print $trace_file Dumper shift; You can then paste in calls to that at the beginning of each function plus sprinkled liberally around the area you're interested in. Use it to dump out execution flow tracing labels, along with variable contents so you can replicate the situation in a test environment.

Then you just need to wait for it to be run, and you can see what it did. Put more than enough detail in the first time, so you're less likely to have to go back in later.

In reply to Re: perl debugging problem by SuicideJunkie
in thread perl debugging problem by perlplayer

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.