One thing I've found useful in debugging is to use levels, e.g.: 
my $debug = 11;
...
print STDERR "something worked: $wombat\n" if $debug > 5;
...
print STDERR "in here: too much detail", join ", ", @_, "\n" 
   if $debug > 20;

[download]
etc. That way I can leave them in until production or later, and bump things back up when I break something. I try to make it a habit to always write debug noise in like that at the start (every "print STDERR ..." line has a debug level) and it works out much easier as the development progresses.

You could add something like that: 

debugprint("now entering mysub ...\n", 11);
sub debugprint($$)
{
  my ($err_str, $debug_value) = @_;
  print $err_str if $debug_value >= $debug;

[download]
or something ...

a

In reply to Re: debugging /logging help by a
in thread debugging /logging help by boo_radley

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.