When it still worked reliably, my heaviest usage Devel::DProf wasn't for the profiling. What I used it the most for was tracing.
The dprofpp -T option would generate a space-indented dump of every single function call made in the program, including all the BEGIN stuff as the program compiled.
It was particularly useful for crashing or failing programs, because you could just start at the end of the trace and then watch the explosion backwards in slow motion, moving back to find the place where it all started to go wrong.
Unfortunately the new king of profilers, Devel::NYTProf, can't replicate this neat trick (yet?).
In the mean time, does anyone have a recommendation of where I can go to get the same information? I can't find anything obvious...