Trying to remember a perl debugging practice

mhearse has asked for the wisdom of the Perl Monks concerning the following question:

I'm trying to recall a perl debugging process that I haven't used in a while. It was a series of commands included with the perl distribution. You would call you program with one command. It would then generate a cryptic temp files with statistics about your program. You would then run another program on that temp file which would summarize the number of function/method calls, the time spent in each call, etc. Does anyone know these commands?

Comment on Trying to remember a perl debugging practice

Replies are listed 'Best First'.
Re: Trying to remember a perl debugging practice by dsheroh (Monsignor) on Feb 08, 2008 at 06:11 UTC
Sounds like you're trying to describe "(code) profiling", quite possibly using Devel::DProf.	[reply]
Re^2: Trying to remember a perl debugging practice by mhearse (Chaplain) on Feb 08, 2008 at 06:38 UTC
Thanks, that's it!	[reply]
Re^3: Trying to remember a perl debugging practice by salva (Canon) on Feb 08, 2008 at 09:12 UTC
There are other interesting profilers available from CPAN, for instance Devel::Profile that's very similar to Devel::DProf or Devel::SmallProf and Devel::FastProf that profile at the source code line level.	[reply]
Re: Trying to remember a perl debugging practice by andreas1234567 (Vicar) on Feb 08, 2008 at 08:52 UTC
perl dprof returns Profiling Perl (Profiling Perl, by Simon Cozens, June 24, 2004) -- Andreas	[reply]
Re: Trying to remember a perl debugging practice by kyle (Abbot) on Feb 08, 2008 at 16:12 UTC
See also Profiling your code.	[reply]