Geoffrey Young wrote:
Jeff wrote:
Not sure if its relevant, but from general Perl usage, Devel::Profiler
often fails to properly recognise function names if its USE statement
ends up being executed before your classes have been USEd.
yes, because Devel::Profiler scans for then during it's import routine.
the behavior is slightly different under mod_perl (the scan is delayed)
No joy with Devel::Profiler::Apache sadly - I couldn't even get it to
write anything out. I tried log dir permissions, tried creating the
'profiler' directory like you have to do for DProf, I even tried
updating Profiler/Apache.pm to use Apache2::ServerUtil instead of
Apache->, and I tried pulling it in with either PerlModule or 'use' -
the only time it even appeared to load was when I tried it with a 'use'
statement on the original code, and of course it complained about the
'Apache' package not existing.
I'll try using DProf again but with a 'use' after all my other stuff is
loaded.
cheers
John
