This seg fault occurs sporadically on the FIRST SSL hit to the server immediatly after startup. Subsequent hits to SSL do not have a problem.
This occurs only with this in the conf: SSLSessionCache shmht:/usr/local/apache/ssl/ssl_cache Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 2051 (LWP 28822)] 0x40260c7c in memcpy () from /lib/i686/libc.so.6 (gdb) where #0 0x40260c7c in memcpy () from /lib/i686/libc.so.6 #1 0x0824c7e0 in ?? () at eval.c:41 #2 0x080a25a4 in ssl_scache_store (s=0x820d808, id=0x827e298 "¹\202pÙ[\222\beÆ;-½\001ýàfS²»\231£Ô¯\031\233üÒ\004¯\017\031. ", idlen=32, expiry=1045611512, sess=0x827e250) at ssl_scache.c:129 #3 0x0809bd32 in ssl_callback_NewSessionCacheEntry (ssl=0x824c7e0, session=0x827e250) at ssl_engine_kernel.c:1732 #4 0x080eb86e in ssl_update_cache () at eval.c:41 Cannot access memory at address 0x2 (gdb) up 2 #2 0x080a25a4 in ssl_scache_store (s=0x820d808, id=0x827e298 "¹\202pÙ[\222\beÆ;-½\001ýàfS²»\231£Ô¯\031\233üÒ\004¯\017\031. ", idlen=32, expiry=1045611512, sess=0x827e250) at ssl_scache.c:129 129 rv = ssl_scache_shmht_store(s, id, idlen, expiry, sess); Digging into this a bit, the memcpy that is faulting is occuring in ssl_scache_shmht.c in ssl_cache_shmht_store on the line which says: memcpy(vp, &expiry, sizeof(time_t)); I'm not sure why this is happening. My debugging indicates that vp is not NULL. I am not very familiar with mod_ssl, so any pointers or suggestions would be welcome. This is happening on 2.0.43 with a statically linked openssl version 0.9.6g on linux 2.4.18 with libc 2.2.4. thanks, -adam -- "I believe in Kadath in the cold waste, and Ultima Thule. But you cannot prove to me that Harvard Law School actually exists." - Theodora Goss "I'm not like that, I have a cat, I don't need you.. My cat, and about 18 lines of bourne shell code replace you in life." - anonymous Adam Sussman Vidya Media Ventures [EMAIL PROTECTED]