On Thu, Jul 26, 2007, Prabhu S wrote: > Hi David, > > I enabled the debug flags in the OpenSSL makefiles and recompiled for the > libraries. > The stack trace is obtained is as follows: > > #0 0x40000402 in __kernel_vsyscall () > #1 0x001fc1f8 in raise () from /lib/libc.so.6 > #2 0x001fd948 in abort () from /lib/libc.so.6 > #3 0x0023152a in __libc_message () from /lib/libc.so.6 > #4 0x00237424 in _int_free () from /lib/libc.so.6 > #5 0x0023795f in free () from /lib/libc.so.6 > #6 0x4057b602 in CRYPTO_free (str=0x640f9c38) at mem.c:378 > #7 0x405e64f5 in ERR_clear_error () at err.c:722 > #8 0x403999ad in ssl3_connect (s=0x63e384c8) at s3_clnt.c:169 > #9 0x403b06ac in SSL_connect (s=0x63e384c8) at ssl_lib.c:850 > > Does it indicate a OpenSSL problem?..I have dug the application code and so > far appears it appears to be clean. >
It isn't immediately clear if that is an OpenSSL problem or not. The error code makes extensive use of locks and thread IDs. If there is a problem with either the locking callbacks or the thread ID callback then that could cause this problem. Steve. -- Dr Stephen N. Henson. Email, S/MIME and PGP keys: see homepage OpenSSL project core developer and freelance consultant. Funding needed! Details on homepage. Homepage: http://www.drh-consultancy.demon.co.uk ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager [EMAIL PROTECTED]
