comment on

To answer your original question 2, the closest you can get with the stock perl debugger is its tracing output.

To enable tracing in the debugger use the t command. You don't get verbose comments like in your example. Instead each executed line is printed with line number information.

The amount of tracing information can be controlled with the frame debugger option. For example you can enable messages for entering/exiting subroutines, show subroutine parameters, show tied and referenced variables, or print the return values of subroutines.

If you want to trace certain sections in your code, you can set the $DB::trace variable to 1 to enable tracing, and to 0 to disable tracing. For details see perldeb

In reply to Re: Debugging a program by hexcoder
in thread Debugging a program by leonidlm

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.


The stupid question is the question not asked
	PerlMonks