On Wed, 26 Jan 2000, Steven Parkes wrote:
> We've been getting many segv's and bus errors on apache processes since
> adding modperl. Env: Apache 1.3.11 (though we had the same thing
> under 1.3.9.), Perl 5.005003, modperl 1.21, hpux 11.00.
>
> At first most of the failures were coming within visit() during what looks
> to be clean up of children. PerlFreshRestart is Off. I added
> PerlSetEnv PERL_DESTRUCT_LEVEL -1
> and that seemed to get rid of many of those though this seems like a less
> than optimal solution and I'd like to better understand what the real
> issue is here.
>
> Moreover, we still see a number of failures. Many seem to occur in __errno.
>
> (gdb) bt
> #0 0xc01ecb88 in kill () from /usr/lib/libc.2
> #1 0x769c8 in sig_coredump () from /usr/local/alpha/apache/bin/httpd
> #2 <signal handler called>
> #3 0xc0179214 in __errno () from /usr/lib/libc.2
> #4 0xc01751bc in free () from /usr/lib/libc.2
> #5 0x10013c in Perl_safefree () from /usr/local/alpha/apache/bin/httpd
> #6 0x112248 in Perl_sv_clear () from /usr/local/alpha/apache/bin/httpd
> #7 0x112478 in Perl_sv_free () from /usr/local/alpha/apache/bin/httpd
a buggy xs modules or c library that overwrites memory can trigger these
problems, seemingly random core dumps in free() or malloc(). do you have
a tool such as purify or insure? they can often identify the problem
right away. otherwise, we need to know more about your setup to help,
what modules you're using, etc.
