Perl: the Markov chain saw | |
PerlMonks |
Re: Profiling forking code?by BrowserUk (Patriarch) |
on Jan 13, 2003 at 18:45 UTC ( [id://226553]=note: print w/replies, xml ) | Need Help?? |
The same question came up a few months ago at Profiling a forking program, but I just took a quick scan of that thread and it didn't seem to suggest any good resolution. The biggest problem seems to be that DProf uses a hard-wired filename for the tracing file 'tmon.out', When I took a look at doing the same thing a little while ago, I thought that I might be able to modify the module so that it incorporated the process ID (or similar) into the output filename, but when I tried to track down the location of the filename, I found it embedded in a /lib/auto/DProf/Dprof.dll which stopped me persuing the idea further. If you built your own version of perl, you might have more luck in modifying the C source of the .dll (or your binary equivalent. I did look at it, but it make heavy use of macros and was non-obvious (to me) where to start. Maybe one of the other Profiling modules I seen mentioned recently but don't recall the name of right now is or could be made more process freindly. Good luck. Examine what is said, not who speaks. The 7th Rule of perl club is -- pearl clubs are easily damaged. Use a diamond club instead.
In Section
Seekers of Perl Wisdom
|
|