Hi, I have an application which has more than 100 SSL client threads and each of those threads tried to connect to a SSL server simultaneously. Occasionally the application process got coredump on the call to ssl_connect(), please see the stack trace below for detail.
*** glibc detected *** testnetwork: double free or corruption (!prev): 0x00002aaaf001adf0 *** ======= Backtrace: ========= /lib64/libc.so.6[0x30896722ef] /lib64/libc.so.6[0x3089674542] /lib64/libc.so.6(realloc+0x102)[0x30896751a2] ~/openssl/lib/libcrypto.so.1.0.0(CRYPTO_realloc+0x60)[0x2b06737c1d80] ~/openssl/lib/libcrypto.so.1.0.0(lh_insert+0x176)[0x2b067382a926] ~/openssl/lib/libcrypto.so.1.0.0[0x2b067382c9c6] ~/openssl/lib/libcrypto.so.1.0.0(ERR_get_state+0x1f9)[0x2b067382cf09] ~/openssl/lib/libcrypto.so.1.0.0(ERR_clear_error+0xd)[0x2b067382d62d] ~/openssl/lib/libssl.so.1.0.0(ssl3_connect+0x31)[0x2b0673529f21] Could someone give me some suggestions about this issue? By the way, in my application, all these 100 SSL client threads share the same SSL_CTX object and the application runs under RedHat Linux. Thanks Bob