Damian Conway gives some excellent Debugging advice
in Ten Essential Development Practices namely:
Add New Test Cases Before You Start Debugging
The first step in any debugging process is to isolate the incorrect behaviour of the system,
by producing the shortest demonstration of it that you reasonably can.
Once you have distilled a short working example of the bug, convert it to a series of tests.
Don't try to fix the problem straight away, though. Instead, immediately add those tests to your test suite.
The point is: if the original test suite didn't report this bug, then that test suite was broken.
It simply didn't do its job (finding bugs) adequately. Fix the test suite first by adding tests that cause it to fail.
Once the test suite is detecting the problem correctly, then you'll be able to tell when you've correctly fixed the actual bug,
because the tests will once again fall silent.
The more thoroughly you test the bug, the more completely you will fix it.
External Debugger References
Perl Monks Debugger Nodes
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||