perl-modperl mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Perrin Harkins <phark...@gmail.com>
Subject Re: first time debugging apache/mod_perl Seg fault
Date Tue, 14 Jul 2009 20:56:58 GMT
Alan,

You might want to try mod_log_forensic to see what the request was
that crashed it.

- Perrin

On Tue, Jul 14, 2009 at 3:29 PM, Alan McKay<alan.mckay@gmail.com> wrote:
>> http://modperlbook.org/html/21-5-8-Noninteractive-Perl-Debugging-Under-mod_perl.html
>
> OK, I'm doing this, but it seems that the file it produces only ever
> gets up to 7.3M and that's it.
>
> I'm guessing it is because when httpd forks off all the children, they
> do not record to this file anymore.
>
> So I try the -X option to prevent apache from forking, but our
> application does not like that very much at all for some reason.
>
> Also, the above link does not show me how to determine from the log
> file where Apache crashed.  All it says is "We will show only the part
> that actually executes the handler created on the fly by
> Apache::Registry:".   OK, so what?   That quote means nothing to me.
> Can someone translate it into something that I understand (assuming it
> is actually something to do with where Apache core dumps)
>
> thanks,
> -Alan
>
>
> --
> “Don't eat anything you've ever seen advertised on TV”
>         - Michael Pollan, author of "In Defense of Food"
>

Mime
View raw message