I've actually found that randomly stabbing in the dark at a bug (aka "thrashing"), although it eventually will usually lead to a solution, is not nearly as effective as taking an extremely rational and logical approach.
Basically, you start at the visible failure condition, and you work backwards until you find the point where things went wrong. Usually, if a bug is hard to find, it's because it's in some area that the programmer assumed couldn't possibly be going wrong ("I already checked the file permissions..."). I have often helped co-workers solve bugs by getting them to test those assumptions.
Ultimately, keeping your cool and staying rational in a stressful debugging situation will usually pay off.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.