You'll need to rebuild your application and openssl with debugging symbols and no optimization, then run it inside gdb to produce a more useful stack trace. Since you don't include any context or source code snippets it isn't really possible to help. Can you produce a reduced test case with source code which reproduces the bug? As long as politics is the shadow cast on society by big business, the attenuation of the shadow will not change the substance. John Dewey: The Later Works, 1925-1953; Volume 6, pp. 163 On Feb 24, 2016 11:33 PM, "Vikas TM" <vikas.tm at gmail.com> wrote: > Hi, > > While running my application with openSSL 102d and I encountered double > free error or corruption. > > As per few threads suggestion, I have changed getpid() with pthread_self() > in CRYPTO_thread_id(). Still the result is same. > > Please let me know if any fix available to this issue. > > *** glibc detected *** xxx: double free or corruption (!prev): 0x097b8750 > *** > > ======= Backtrace: ========= > > /lib/libc.so.6[0x1768b6] > > /lib/libc.so.6(cfree+0x90)[0x179e00] > > xxx(CRYPTO_free+0x3a)[0x81b89be] > > xxx(ssl_cert_free+0x13f)[0x826fa23] > > xxx(SSL_free+0x14d)[0x81d7e08] > > Thanks & Regards, > Vikas > > -- > openssl-users mailing list > To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mta.openssl.org/pipermail/openssl-users/attachments/20160225/d63485b8/attachment.html>
