On Sun, Jan 10, 1999, [EMAIL PROTECTED] wrote:
> Full_Name: Andreas Karajannis
> Version: 2.1.6
> OS: Linux
> Submission from: kara.gmd.de (129.26.240.27)
>
> Enabling the session cache leads to core dumps.
> gdb backtrace:
>
> Core was generated by `/usr/local/apache/sbin/httpd'.
> Program terminated with signal 11, Segmentation fault.
> #0 0x400d6e2d in ?? ()
> (gdb) bt
> #0 0x400d6e2d in ?? ()
> #1 0x8067615 in ssl_scache_dbm_retrieve (s=0x20, SCI=0x81cf6d8) at
> ssl_engine_scache.c:322
> #2 0x20 in ?? ()
> #3 0x6095634a in ?? ()
> Cannot access memory at address 0xe92c75c8.
Hmmm... this has to be a local problem, because the cache stuff wasn't changed
for a longer time and I've never seen it broken in the past. So, I guess that
either your NDBM library or SSLeay is the problem. Perhaps SSLeay is build
incorrectly? Is this a x86 Linux platform or a different CPU platform?
And have you configured SSLeay with just "gcc" as the platform name or with
"linux" or with what exactly? At least we need to know a little bit more
information in the the backtrace. Can you rebuild SSLeay _and_ Apache+mod_ssl
with "-g -gdb3" and then try to analyze the backtrace again?
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]
