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

use Perl Log In

Log In

[ Create a new account ]

Ovid (2709)

Ovid
  (email not shown publicly)
http://publius-ovidius.livejournal.com/
AOL IM: ovidperl (Add Buddy, Send Message)

Stuff with the Perl Foundation. A couple of patches in the Perl core. A few CPAN modules. That about sums it up.

Journal of Ovid (2709)

Monday July 16, 2007
02:36 AM

Debugger scripts

[ #33815 ]

OK, I've complained about this before, but I (or someone else) really, really needs to write this for collaborative endeavors.

  1. perldebug some_code -o replay_bug.pdb
  2. b 109
  3. c
  4. s
  5. b _runtest
  6. n
  7. n
  8. n
  9. x $self->_get_parser_args($test)
  10. n
  11. x $self
  12. q

You then attach replay_bug.pdb and email it to your collaborator or to P5P or something and they do this:

  1. perldebug < replay_bug.pdb

At that point, I would want it to recognize whatever's in the replay file, run any commands and create diffs of the output for developers to analyze.

The replay file should contain all debugger commands run (including support for Devel::ebug?), and STDOUT and STDERR.

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.