I am trying to profile a large app made from a combination of a large number of perl modules and a thin layer of mason components.
I have tried starting apache with -C 'PerlModule Apache::DProf 'or -C 'PerlModule Devel::Profiler::Apache' — I get no errors, but I also get no profile files created.
I know that's not a lot of information, but with no errors and no output I'm stumped for what to look for! Has anyone had to solve this before? I suppose I can debug the runnig process and see if the handlers are registered etc. Could my problem be that the handler is registered after Mason? I have tried using -C and -c for different startup order to no avail.
gah.
Mark.
In reply to Profiling under mod_perl by aufflick
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |