comment on

If so, where should that focus begin?

I would focus on solving an actual problem (actual debugging), not teaching perl5db -- learning perl5db commands should be a side-effect of solving a problem using perl5db

I understand this may be more ambitious undertaking :)

Why? Because I've learned some debugger commands, but I still do my debugging with print ( Data::Dump::dd actually ), maybe you can teach me something?

Its like every $language-oop tutorial, teaches the how not the why, what each button does, not when to use it -- good examples can do both

speaking of perl5db :) have you seen ebug/ebug_wx?

Are debuggers good? Well, you can't debug everything with them :) ( Preventing BEGIN blocks from being run in the debugger? )

In reply to Re: RFC: debugger_trainer by Anonymous Monk
in thread RFC: debugger_trainer by ww

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.


laziness, impatience, and hubris
	PerlMonks