On Wed, Oct 04, 2000 at 02:58:40PM -0700, David Rees wrote:
> I finally found some time to get a debugger on the apache processes, and do
> some load testing until one of the children sigbussed. It seems that
> leaving the debugger on caused most of them to sigbus, and eventually some
> children started showing sigsegv in another section of code.
My guess is that the SIGBUS is probably something that happens because
you've got it running under the debugger. The SIGSEGV more looks like
the real problem here - I'm no expert at reading debugger output ;-) but
it looks like the problem is in adding entries to the session cache, when
adjusting the size of the table/buckets. I haven't looked too closely at
the code yet, but a guess would be that you're filling up the session
cache. What if you run with SSLSessionCache none - does it still segfault?
vh
Mads Toftum
--
`Darn it, who spiked my coffee with water?!' - lwall
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
