in reply to Re: Profiling under mod_perl
in thread Profiling under mod_perl

Nope - tried that. No dice...

I suspect that my mason handler is connecting to mod_perl higher (or earlier - depending on your mental model) and thus is being excluded as part of the startup.

Replies are listed 'Best First'.
Re^3: Profiling under mod_perl
by perrin (Chancellor) on Feb 22, 2005 at 00:09 UTC
    Put this in your httpd.conf before anything else that loads a perl module:
    <Perl> require Apache::DB; Apache::DB->init; </Perl>
      Hmm - it seems like a good suggestion, since that's how you initialise running apache through the perl debugger (plus you add PerlFixupHandler Apache::DB of course...) and the profiling code uses the same debugger hooks.

      But when I do that combined with PerlModule Apache::DProf Apache actually exits (with no error) on the first request...

        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.