The people have have tried to convince me to use one or another debugger are usually the sort that work on single scripts and modules from only CPAN (so they aren't debugging their own modules).

Odd. I found the perl debugger especially valuable for deciphering other people's modules, especially for bugs in CPAN modules.

For example, about four or five years ago, there was a bug in one of the PDF modules we were using; the author had clearly forgotten the /g modify on one of his regexps, so that only the first occurance of a given class of special characters was being properly escaped.

I didn't have to grasp the entire PDF specification, nor the author's intent in implementing that specification, in order to detect and correct the bug, because I had a nice debugger to guide me, and show me what was going on inside all the tricky objects and methods and twisty maze of function calls.

Especially with OO, where a function can return objects from different classes, each of which has their own special version of a method call, it's very nice to know exactly what function is being called, and which data is being passed, when all the code says is "call method X with object Y".

In reply to Re^2: I never use the debugger. by Anonymous Monk
in thread I never use the debugger. by friedo

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.