Not yet mentioned: If everything fails, there's always the lowlevel approach of using the perl -d, type s<CR>, then keep <CR> pressed: this should give you the the last few lines of code before it dies, and thus an idea what actually happens. Maybe with a suitable breakpoint to speedup reaching the problematic line. man perlrun, man perldebug. Printing the arguments of the dying function call might also help -> perldoc -m Data::Dumper once again.
Meta: shouldn't there be an existing help/faq node on basic debugging; or do we assume this to be well-known?
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
Outside of code tags, you may need to use entities for some characters:
- 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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||