We've already recognized that on some not-such-smart platforms Apache+mod_ssl
can dump core under the DSO situation. I've already traced it down and the
problem has to do with the fact that Apache _reloads_ the DSOs at startup-time
and that some dangling references to EAPI hooks exists this way. On platforms
like FreeBSD and Linux (where I develop mod_ssl) the modules always seem to be
reloaded to the same memory address, so I never recognized this problem. But
now Khimenko Victor's EAPI replacement patches gave me the essential hint that
the hooks are not unregistered correctly. This doesn't harm when the module
was reloaded to the same address, but causes core dumps when this isn't the
case.
I've already fixed this for the forthcoming mod_ssl 2.1.8 except for a very
complicated case (where mod_log_config is involved). So I need a little bit
more time. In the meantime when you still have the "I want to install Apache
1.3.4 + mod_ssl, but it still dumps core" problem for you just build mod_ssl
_STATICALLY_ (i.e. don't use --enable-shared=ssl). This way it should be
fine. At least I've never seen core dumps when mod_ssl is built statically
myself and also AFAIK there are no other reports from people who have these
problem this way.
I hope I can finally fix this for 2.1.8, but as I said, it needs more time.
So either be patient or in the meantime build mod_ssl without DSO when you've
such problems. Thanks.
Greetings,
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/
Official Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
