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=1 appears to be > needed on FreeBSD): > > (gdb) bt > #0 0x28384eb4 in strncpy () from /lib/libc.so.7
> #1 0x287af9ee in modperl_perl_global_avcv_clear () > from /usr/local/libexec/apache22/mod_perl.so > #2 0x287afacf in modperl_perl_global_avcv_clear () > from /usr/local/libexec/apache22/mod_perl.so That's odd, modperl_perl_global_avcv_clear should not be able to call itself. It looks like you don't have debugging symbols for mod_perl itself, could you get that as well, as it would show me a little bit more as to what's being double-freed, looks like. Also, you can just try and run your test case with MOD_PERL_TRACE='g' in your environment ? It turns on global handling debugging output. error_log would contain information about what is going on in more details. -- Philippe M. Chiasson GPG: F9BFE0C2480E7680 1AE53631CB32A107 88C3A5A5 http://gozer.ectoplasm.org/ m/gozer\@(apache|cpan|ectoplasm)\.org/
signature.asc
Description: OpenPGP digital signature
