> I just found and fixed a long standing bug in SSL locking.
> The problem was that both, the client and the server context
> used the same SSL locking callback function. Unfortunately
> this function referenced only one set of mutexes. The fresh
> and shiny server mutexes never got used.
> On shutdown the SSL server code then tried to access the already
> released client SSL mutexes which caused the crash on shutdown.
>
> The fix is obvious: use a separate callback for the server context.
> This is implemented and in CVS.
thanks Jörg, this has been obviously my fault :(
Stipe
[EMAIL PROTECTED]
---
Wapme Systems AG
Münsterstr. 248
40470 Düsseldorf
Tel: +49-211-74845-0
Fax: +49-211-74845-299
E-Mail: [EMAIL PROTECTED]
Internet: http://www.wapme-systems.de
---
wapme.net - wherever you are
