On Tue, May 30, 2006, Steffen Weinreich wrote:

> Ralf S. Engelschall schrieb:
> >     1. SSLSessionCache  shmht:[...filename...](512000)
> >     2. SSLSessionCache  dbm:[...filename...]
> >     3. SSLSessionCache  none
> >
> > If the problem goes away already with (1) the SHMCB code is the problem.
> > If the problem goes away with (2) I would be surprised. If the problem
> > goes away with (3) the session cache framework is the problem and would
> > be surprised even more. I guess the problem either goes already away
> > after (1) or persists even after (3).

> It went away with (1). If I interpret your mail correctly the problem
> is somewhere in the shmcb(shared memory callback?) code?

Yes, this means there is a problem in the mod_ssl SHMCB code. And as
the code works fine for a long time and on lots of platforms I do not
think it is a simple semantic error inside the code. I'm rather sure
it is either related to some invalid casts (which for still unknown
reasons trigger the problem just on Solaris 10/sparc64) or it contains
code which triggers a compiler code generation bug. The problem is that
this is very hard (or nearly impossible) to fix without proper debugger
support. Either "gdb" allows us to single-step the code or we have to
take the largest hammer and splice in a large bunch of printf()s (which
don't require any debugger support and work under "-O2" just fine)...

                                       Ralf S. Engelschall
                                       [EMAIL PROTECTED]
                                       www.engelschall.com

______________________________________________________________________
The OpenPKG Project                                    www.openpkg.org
Developer Communication List                   openpkg-dev@openpkg.org

Reply via email to