On Thu, 31 Dec 2009, Philippe M. Chiasson wrote:
On 09-12-31 12:52 , Alex Aminoff wrote:
Most certainly, yes. A stack trace without debugging symbols is not
very useful in trying to pin down the source of a segfault bug.
OK, I compiled mod_perl with MP_DEBUG and MP_TRACE, and
got apache t
On 09-12-31 12:52 , Alex Aminoff wrote:
>
>> Most certainly, yes. A stack trace without debugging symbols is not
>> very useful in trying to pin down the source of a segfault bug.
>
> OK, I compiled mod_perl with MP_DEBUG and MP_TRACE, and
> got apache to produce a core dump (kern.sugid_coredump
Most certainly, yes. A stack trace without debugging symbols is not
very useful in trying to pin down the source of a segfault bug.
OK, I compiled mod_perl with MP_DEBUG and MP_TRACE, and
got apache to produce a core dump (kern.sugid_coredump=1 appears to
be needed on FreeBSD):
(gdb) bt
#0
On 09-12-30 16:28 , Alex Aminoff wrote:
>
> 1. Problem Description:
>
> Our production apache22/mod_perl2 web server segfaults regularly. I
> have tracked down this problem as much as I can, and could use some
> help. This is running on FreeBSD; the same problem occurs on FreeBSD
> 7.0, 7.2, and
1. Problem Description:
Our production apache22/mod_perl2 web server segfaults regularly. I
have tracked down this problem as much as I can, and could use some
help. This is running on FreeBSD; the same problem occurs on FreeBSD
7.0, 7.2, and 8.0. apache22 is installed from ports, with WITH_DEBU
