Hi Andy Our configure option is:
./Configure enable-ssl2 -DSSL_ALLOW_ADH --prefix=/usr --openssldir=/var/ssl no-idea no-rc5 no-symlinks shared threads aix64-xlc_r And in 1.0.2h Configure file, we have: "aix64-xlc_r", "cc:-q64 -O -DB_ENDIAN -qmaxmem=16384 -qro -qroconst::-qthreaded -D_THREAD_SAFE:AIX::SIXTY_FOUR_BIT_LONG RC4_CHAR:${ppc64_asm}:aix64:dlfcn:aix-shared::-q64 -qmkshrobj:.so.\$(SHLIB_MAJOR).\$(SHLIB_MINOR)::-X 64", Thanks Regards Sandeep On Mon, Aug 22, 2016 at 2:36 AM, Andy Polyakov via RT <r...@openssl.org> wrote: > Hi, > > > We are using libcurl for REST programming, which internally uses openssl > > and libcrypto. > > curl suggested to implement few callbacks related to locking, which would > > be needed for openssl below 1.1 version(which is still in beta). > > > > The following callbacks were implemented: > > > > https://curl.haxx.se/libcurl/c/threaded-ssl.html > > > > lock_callback, thread_id, init_locks, kill_locks > > > > With these modifications we are facing a crash in openssl library when > used > > on a Power8 Hardware (with optimizations). > > The fact that it's affected by optimizations is likely to be > circumstantial. I'm not convinced that it's not MT problem with your > application, and whether or not crash is triggered is question of > delicate yet unfortunate timing. And that's what is affected by > optimizations, timing. Questions are. You say you implement the > callbacks, but are they actually engaged? Is your openssl actually > compiled with threads support? Which configuration target/config line > was used to compile it? > > > -- > Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4647 > Please log in as guest with password guest if prompted > > -- Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4647 Please log in as guest with password guest if prompted -- openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev