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?
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|