Beefy Boxes and Bandwidth Generously Provided by pair Networks
more useful options

Re: RFC: Basic debugging checklist

by jplindstrom (Monsignor)
on Feb 19, 2009 at 01:30 UTC ( [id://744925]=note: print w/replies, xml ) Need Help??

in reply to RFC: Basic debugging checklist

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 confess("title: ($title)") # 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 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 #or, depending on the shell/CMD export PERL5OPT=-MCarp::Always set PERL5OPT=-MCarp::Always

Or from within Emacs using the M-x setenv function. This is useful if you run Perl programs using the *compilation* mode.


Log In?

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://744925]
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others pondering the Monastery: (6)
As of 2024-04-21 21:44 GMT
Find Nodes?
    Voting Booth?

    No recent polls found