perl-modperl mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Perrin Harkins <>
Subject Re: first time debugging apache/mod_perl Seg fault
Date Wed, 15 Jul 2009 16:44:39 GMT
On Tue, Jul 14, 2009 at 3:29 PM, Alan McKay<> wrote:
> 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)

I haven't used this tracing feature, but the quote in the book is just
saying that he's showing only the beginning of the trace because it's
too long to reproduce there.  You would be able to see where the crash
happened because the trace would simply end.there.

- Perrin

View raw message