Occasionally, when I have a Heisenbug in a script that resists walk-throughs with 'perl -d', I'll do something like this: 

### At the top of the script
my $debug = 1;                  # Set to '0' to disable debugging outp
+ut

sub debug {
    warn "DEBUG ($_[0]): <<<$_[1]>>>" if $debug;
}

[...]

### Some troublesome variable or value
debug('$foobar', $foobar);

[download]

For really stubborn bugs, I open a log file and write it to the log via 'Data::Dumper'. For that class of bug, I haven't yet found one that can beat that particular treatment. 


-- 
Human history becomes more and more a race between education and catastrophe. -- HG Wells

In reply to Re: Module implementing modified comment-style debugging. by oko1
in thread Module implementing modified comment-style debugging. by Socrates

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.