If you're not able to check out the code to add print statements, how will you fix any bugs that you find?
Otherwise I was going to suggest that, at the points in the module where you want the debugger to break, you add the line:
$DB::single = 1
(That's like hitting 's' in the debugger right at that line.)
This might help with setting breakpoints in the module: you can change which file you're looking at/setting breakpoints in/etc. by using the debugger's 'f' command.
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>
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
Want more info? How to link or
or How to display code and escape characters
are good places to start.