If you're running a straight Perl application (not embedded within Apache/mod_perl), the only other thing I can think of is
Devel::SmallProf. Although it is much more granular than
Devel::DProf, if you claim it's not jumping processes than I would imagine the same fault would be in
Devel::SmallProf. Although you may run into the same issue, it's (should be) a one-line change and worth checking out.
This being said, if you are working within Apache/mod_perl, I have had great success with
Devel::DProf and
Apache::SmallProf. Also, if you are running Linux or any other pre-fork worker, I can all but guarentee the profiler will attach to each post-forked child in order to profile them individually.
Other than that I think you may be out of luck... next to modifying DProf on your own :)
---hA||ta----
print$_ for(map{chr($_)}split(/\s+/,join(/\B?:\w+[^\s+]/,<DATA>)));
__DATA__
67 111 100 101 32 80 101 114 108
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.