Just using "b" (set breakpoint) and "B" (delete breakpoint) will also save you tons of debugging time: you provide a line number or a subname (e.g. "b 384" or "b bigsub"), and you can even add a condition (e.g. "b 384 (!defined $hit)". I often set a bunch of breakpoints before starting a script that has a set of "interesting" branches.

Then do "c" (continue), and it will stop if/when it gets to any breakpoint. If the script has "use Data::Dumper", you can do "p dumper( $ref_variable )" to see how (some portion of) your data structure looks at that point.

And that is just the tip of the iceberg.

In reply to Re^4: foreach in HoHoA problems by graff
in thread foreach in HoHoA problems by mdunnbass

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.