Devel::DProf is a wonderful module. It's also a petulant brat and is given to segfault if it thinks you're looking at it funny. My experience with this love/hate relationship has led me to believe that a quick recompilation of Perl is all that is required to fix the latest segfault I'm facing.

Recompiling Perl is not an option available to me at work. Do you have any recommendations for profiling? Devel::SmallProf seems too fine-grained and the only other thing I can think of is to spider the symbol tables and add pre and post hooks to time all subroutines. That seems just awful to me (not to mention that the timing routines will throw the times off). There has got to be a better way.

Cheers,
Ovid

New address of my CGI Course.

In reply to Profiling without Devel::DProf by Ovid

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.