A simple tutorial about effectively using pdb. Contribute to spiside/pdb-tutorial development by creating an account on GitHub.

You should write your own debugger!

~25:00

https://speakerdeck.com/rjbs/1-dot-21-gigawatts?slide=174

95% of all debugging is print statements, but once or twice a year, a problem shows up that is best attached with perl5db.pl, the venerable core Perl 5 debugger. Like a light saber, it dates back to a forgotten time and its operations are poorly understood. Unlike a light saber, it is not elegant, and nobody aspires to use it. Also, it can cut limbs right off. Still, it’s a very useful multi-purpose tool, and if you learn how to use it, it can save a lot of time and clear up a lot of mysteries.

This talk will cover what the debugger is, how to use it at a basic and intermediate level, how to customize it, and at least one or two stories about how it is very, very awful.

Eugen Konkov — 45 minutes 🐪

Interactive debugging.

This talk about how to catch and report perl application exceptions.

An example based on Mojolicious web server will be given.
I will show how to reproduce exceptions and debug them.
The example will describe how to access and view data at any stack frame.

Also I will show how to implement new debugger commands and how to debug them (yeah, you understand right: how to debug perl debugger while debugging)

This talk will about my second proprietary debugger. It is full rewrite of first version: https://github.com/KES777/Devel-DebugHooks

If you want to try it add the following to $HOME/.perldb:

$DB::alias{dp} = 's/dp/DB::dp/';
sub DB::dp {
    eval {
        require Data::Printer;
        Data::Printer->import(colored=>1,use_prototypes=>0);
    };
    if ($@=~/Can't locate/) {
        print 'Data::Printer is not installed';
        return;
    };
    print Data::Printer::p(@_);
}

perl-stacktrace prints Perl stack traces of Perl threads for a given Perl process. For each Perl frame, the full file name and line number are printed.