Hi, It was seen that the CRYPTO_thread_id() uses getpid() which was returning same value for all threads. Instead of getpid() I used pthread_self() which appears to have solved the problem that I had reported in this mail. I am not seeing the problem re-occur. Another users post referrring to the same case can be found at http://www.mail-archive.com/[EMAIL PROTECTED]/msg21031.html.
I use the linux kernel 2.6 Is using pthread_self() OK. Or is there any better way which would yeild correct thread IDs in CRYPTO_thread_id()? Regards, Prabhu. S On 8/1/07, Prabhu S <[EMAIL PROTECTED]> wrote: > > I shall use the tool to get more insights. In line with the issue > reported(application crash if too many simultaneous SSL handshake occurs) , > I am seeing application crash under stress performance(with valid SSL > sessions). The stack trace is quite identical to posted earlier: > > #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 0x4057d602 in CRYPTO_free (str=0x9dc98360) at mem.c:378 > #7 0x405e84f5 in ERR_clear_error () at err.c:722 > #8 0x403999ad in ssl3_connect (s=0xa0d6aa58) at s3_clnt.c:169 > #9 0x403b06ac in SSL_connect (s=0xa0d6aa58) at ssl_lib.c:850 > > About 600 threads keep connecting to server in a cyclic manner. > > Thanks, > Prabhu. S > > On 7/27/07, Darryl Miles <[EMAIL PROTECTED]> wrote: > > > > 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 only indicate that OpenSSL was the user freeing the memory at the > > time glibc detected a problem. Glibc's detection of these problems is > > not fool proof, maybe you should look at valgrind (but dont forget to > > compile OpenSSL with -DPURIFY) before using the package. > > > > Darryl > > > > > > ______________________________________________________________________ > > OpenSSL Project http://www.openssl.org > > User Support Mailing List openssl-users@openssl.org > > Automated List Manager [EMAIL PROTECTED] > > > >
