Another handy trick (if you don't mind modifying the source and are focusing on a particular piece of code) is to set $DB::single to a true value which will act as if you'd put a breakpoint at that line.
Alternatives to the debugger proper: check out Smart::Comments which will let you get debugging dumps when you run using that module (it's a moderately ebil source filter, but unless you've enabled the module they're just plain text comments). Or use Log::Log4perl and liberally sprinkle DEBUG(qq{intresting value:}, $interesting) statements throughout your code; when you no longer need them, just reduce the log level to (e.g.) INFO instead and those disappear (but they're still there and can be turned back on at will by tweaking a config/log level).
The cake is a lie.
The cake is a lie.
The cake is a lie.
-
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.
|
