Re: Apache::DProf problems

2003-08-30 Thread Brian Hirt
i'll double check, but i'm fairly certain it's loaded first. what if a module is loaded after the fact, but like this: eval { use $module }; some modules are dynamically loaded at run time depending on certain situations. On Friday, August 29, 2003, at 04:26 PM, Stas Bekman wrote: Brian

Re: Apache::DProf problems

2003-08-30 Thread Perrin Harkins
On Sat, 2003-08-30 at 15:34, Brian Hirt wrote: i'll double check, but i'm fairly certain it's loaded first. If you post your conf, we could probably help you more. what if a module is loaded after the fact, but like this: eval { use $module }; Doesn't matter. You just have to initialize

Apache::DProf problems

2003-08-29 Thread Brian Hirt
I've installed Apache::DProf, but it seems hardly any of the calls are profiled. dprofpp shouws MOF::Dispatcher::handler as taking up 100% of the time, but there is no information recorded in for calls within that function. MOF::Dispatcher::handler is calling thousands of other functions

Re: Apache::DProf problems

2003-08-29 Thread Perrin Harkins
On Fri, 2003-08-29 at 17:11, Brian Hirt wrote: I've installed Apache::DProf, but it seems hardly any of the calls are profiled. You probably compiled that code before you initialized the debugger. Add a call to Apache::DB-init before you load your modules, as described in the Apache::DB docs.

Re: Apache::DProf problems

2003-08-29 Thread Stas Bekman
Brian Hirt wrote: I've installed Apache::DProf, but it seems hardly any of the calls are profiled. dprofpp shouws MOF::Dispatcher::handler as taking up 100% of the time, but there is no information recorded in for calls within that function. MOF::Dispatcher::handler is calling thousands of