Hi All, 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, David


"The dead do not recognize context" -- Kai, Lexx

In reply to Simplifying dprofpp Output by djantzen

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.