On Sun Feb 03 19:14:05 2013, m...@netbsd.org wrote:
>
> Here is the first EVP_PKEY_meth_free(0xbb1d0f94) call backtrace:
> #0 EVP_PKEY_meth_free (pmeth=0xbb1d0f94) at
> /openssl/crypto/evp/pmeth_lib.c:294
> #1 0xbb7407c6 in engine_pkey_meths_free (e=0xbb2e8f90) at
> /openssl/crypto/engine/tb_pkmeth.c:163
> #2 0xbb778038 in engine_free_util (e=0xbb2e8f90, locked=1) at
> /openssl/crypto/engine/eng_lib.c:129
> #3 0xbb7780c2 in ENGINE_free (e=0xbb2e8f90) at
> /openssl/crypto/engine/eng_lib.c:142
> #4 0xbb6dc4eb in ENGINE_load_gost () at
> /openssl/engines/ccgost/gost_eng.c:269
> #5 0xbb6d2e9a in ENGINE_load_builtin_engines () at
> /openssl/crypto/engine/eng_all.c:117
>
> The patch below avoid the crash, but worsen the leak as no
> EVP_PKEY_meth_free() are called anymore.
>

Have you tried a recent snapshot of OpenSSL 1.0.1 tree?

This might fix it:
http://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=d21bf10dea6588b632a65b4fe594e04f288aad83;hp=d47c01a31a67ff4370b1883a58cabd0279752bb4

--
Dr Stephen N. Henson. OpenSSL project core developer.
Commercial tech support now available see: http://www.openssl.org

______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Development Mailing List                       openssl-dev@openssl.org
Automated List Manager                           majord...@openssl.org

Reply via email to