Re^5: Profiling under mod

You are probably getting segfaults. Devel::DProf is notorious for that.

You would probably get better help if you post the problem, including details of your setup as described in the "reporting bugs" section of the website, to the mod_perl mailing list.

Comment on Re^5: Profiling under mod_perl

Replies are listed 'Best First'.
Re^6: Profiling under mod_perl by aufflick (Deacon) on Feb 22, 2005 at 00:36 UTC
Good idea about the mod_perl mailing list. I would have figured a segfault (I am all to familiar with the frailty of DProf), but Devel::Profiler::Apache is doing the same thing, and not a core file to be found anywhere. I genuinely think it is doing nothing... but I will head out from the monastry (hopefully with some nice beverage that monastries were famous for in the old days) and trek over to the mod_perl mailing list...	[reply]
Re^7: Profiling under mod_perl by perrin (Chancellor) on Feb 22, 2005 at 01:48 UTC
One more thing: make sure that the user your server runs as is able to write to the directory that the file should end up in.	[reply]
Re^8: Profiling under mod_perl by aufflick (Deacon) on Mar 01, 2005 at 00:47 UTC
yaha - Of course... since the dprof file is written by the child, not the master, the effective user is not root and thus has no write access to the apaceh root. Solution is to add the following to the httpd command line: -d `pwd` Of course a non-dev situation would require something other than pwd, but you really shouldn't be profiling a production system ;) Thankyou - mods up everyone.	[reply] [d/l]