Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • by da (1525) on 2005.11.14 15:29 (#44527) Homepage Journal
    $DB::single = 1; could be inserted into the module code for Some::Module::... to stop it at the right point.

    I've done the lazy version of a script, copy-and-paste 20 lines of debugger commands at a time to re-run them. It's inelegant, but like you, I took a look at the debugger code and averted my eyes :) However, I just took a glance at perldebug, and it says:

           You can mock TTY input to debugger by adding arbitrary commands to
           @DB::typeahead. For example, your .perldb file might contain:

               sub afterinit { push @DB::typeahead, "b 4", "b 6"; }

           Which would attempt to set breakpoints on lines 4 and 6 immediately
           after debugger initilization. Note that @DB::typeahead is not a sup-
           ported interface and is subject to change in future releases.
    I'm curious how well that works.
    --

    -DA [coder.com]

    • in 2003, mjd worked on the debugger under a perl foundation grant, which was to include a deliverable of a refactored debugger.

      http://www.perlfoundation.org/gc/grants/2003_q4.html

      That would be very, very, cool if the code were available for hacking on... I haven't been able to find it, in quick google searches; I suppose I should email mjd. :)
      --

      -DA [coder.com]