rockyb

• About: I blog about Perl.

Recent Actions

• Commented on A plan for revamping and replacing the Perl debugger.
  Thanks for the correction. perl5db.pl in Perl 5.16.1 has only 9,493 lines; so 10K lines is a little a slight overstatement. But the point I was trying to make (and 10K bytes doesn't do it) still holds: that this is...
• Commented on A plan for revamping and replacing the Perl debugger.
  Let's work together on this. When I browsed the github repository there seems to be a layer of dealing with sockets and parsing text output that should its own separate Module. In fact it would be the same thing you'd...
• Commented on A plan for revamping and replacing the Perl debugger.
  First, let me say that if you are happy with the existing debugger, inspection, or just using print statements or whatnot, great! But as for why others want to improve perl5db, see for example this perl foundation project which was...
• Posted A plan for revamping and replacing the Perl debugger. to rockyb

  There is a little bit of overlap here with the first blog on Devel::Trepan. I apologize for that, but I don’t see how this can be avoided. The focus here though is more on the existing Perl debugger rather than Devel::Trepan which is given as one concrete example from which to draw…

• Posted Devel::Trepan 0.31 release to rockyb

  A new release of Devel::Trepan is out there.

  A number of changes were the result of problems found in writing the various debugger blogs and in preparing for a little local ="http://w…

• Posted Location, Location, Location to rockyb

  By way of explanation...

  In preparing this and my previous blogs, I have noticed aspects where Devel::Trepan could be improved. For this blog, I discovered when comparing Devel::Trepan output with that from a recent

• Posted To gdb or not to gdb? to rockyb

  Whether 'tis nobler in the mind to suffer
  Or to take arms against a sea of troubles

  Spoiler alert: the answer is 1 or true

  Before delving back in the next planned blog post of another important nuts-and…

• Posted Devel::Trepan Debugger evaluation of Perl statements to rockyb

  In the last blog, I started describing features that are new in Devel::Trepan that aren't in perl5db.…

• Posted Devel::Trepan Debugger command aliases and command completion to rockyb

  In my first blog I described why I wrote a new debugger for Perl and how the rewrite helps me add cool features more easily. Here I'll start to describe the cool features of this debugger. To…

• Posted On writing a new Perl Debugger (Part 1 - Why?) to rockyb

  This is the first part of what will be several parts. The next part may be more interesting to a general audience: what are some of the cool new features of the debugger? …

Comment Threads

• kablamo commented on A plan for revamping and replacing the Perl debugger.

  I would like to see a debugger api. I've been working on Vim::Debug and an api would make integrating the debugger with Vim a lot more fun.

  I suppose the way to do that these days would be to embed a Plack app in trepan?
  

• Olivier Mengué (dolmen) commented on A plan for revamping and replacing the Perl debugger.

  Fix: perl5db.pl is not a 10K file. This is a 10K lines file.

• dagolden.com commented on A plan for revamping and replacing the Perl debugger.

  I'm really pleased to see progress on replacing the debugger with something less monolithic and more flexible.

  As for how it's done, I think packaging up the old debugger as a dual life module is a good step so that those who still want it will eventually be able to install it from CPAN.

  This is similar to what happened with Devel::DProf when it was superceded by Devel::NYTProf (though that isn't itself in the core).

• happymorning commented on A plan for revamping and replacing the Perl debugger.

  You may check Devel::ebug ; it's a module that provide a clean API over the perl debugger.