I admit that I rarely use the debugger as it's intended to be used, but I find that I often use the debugger as a perl REPL, (Read-Eval-Print Loop) to do some quick manual testing of a new sub. Just run
perl -d somefile.pl, and then type
p mynewfunc('testvalue') to see the output.
I guess I should add by way of context that most of the perl code we write around here isn't object oriented at all, it's just long driver scripts being used to kick off the "real" processing code. As such, it's almost all standalone scripts, so the debugger is really the easiest (and fastest) way to load up a file and invoke pieces of it when the file was not necessarily designed to be invoked piecemeal.
--
@/=map{[/./g]}qw/.h_nJ Xapou cets krht ele_ r_ra/;
map{y/X_/\n /;print}map{pop@$_}@/for@/