I'm trying to use dprofpp and the Devel::DProf to debug a set of modules. I run the script with
perl -d:DProf script.pl
to generate tmon.out
, then use dprof with the -T option to get a nice call tree output. The problem is that the resulting file is close to 38,000 lines long, mostly with not so useful stuff like BEGIN and DESTROY blocks, thousands of DBI calls, and some calls to other sections of our codebase I don't care about. Is there any way to simplify the output to something usable, say, to give a list of modules to which subroutines must belong in order to show up in the output? Or maybe someone else has written a tool for filtering the output? At this point I'm thinking I may end up just writing a script to filter by module name myself. Any gotchas you can think of?
Thanks in Advance,
"The dead do not recognize context" -- Kai, Lexx