Use the Carp module to show you the stack trace, i.e. each sub routine call in the source code from which you started the program to where you are printing the debug output. Carp comes with Perl.
use Carp qw/ cluck confess longmess /;
# die of errors with stack backtrace
# warn of errors with stack backtrace
cluck("Before escaping title ($title)");
$title = $self->escape($title);
cluck("After escaping title ($title)");
# longmess - return the message that cluck and confess produce
$self->log_error( "title not set: " . longmess() );
Carp on search.cpan.org appears to identify perl itself and doesn't provide POD for some reason, but see: perldoc Carp.
Another useful module is Carp::Always, which makes all dies and warns emit stack traces.
Note that this will change exception strings, so any eval BLOCK that checks for specific exception matches against $@ may fail because of this.
Enable Carp::Always with a regular "use" statement in the code, or temporarily from the command line using one of these:
perl -MCarp::Always your_program.pl
#or, depending on the shell/CMD
Or from within Emacs using the M-x setenv function. This is useful if you run Perl programs using the *compilation* mode.
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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||