> [[email protected] - Thu Apr 01 11:00:08 2010]: > > Under certain circumstances, this turns into segfaults: > > Program received signal SIGSEGV, Segmentation fault. > 0x4108a6a5 in free () from /lib/libc.so.6 > (gdb) bt > #0 0x4108a6a5 in free () from /lib/libc.so.6 > #1 0x4141e06e in CRYPTO_free (str=0x39) at mem.c:391 > #2 0x414e525a in EVP_PKEY_asn1_free (ameth=0x82c0b48) at > ameth_lib.c:386 > #3 0x414a0787 in engine_pkey_asn1_meths_free (e=0x39) at > tb_asnmth.c:165 > #4 0x4149c233 in engine_free_util (e=0x822dee0, locked=0) at > eng_lib.c:130 > #5 0x4149ca28 in ENGINE_remove (e=0x822dee0) at eng_list.c:187 > #6 0x4149ca9e in engine_list_cleanup () at eng_list.c:88 > #7 0x4149c0cb in engine_cleanup_cb_free (item=0x8242060) at > eng_lib.c:186 > #8 0x414b0340 in sk_pop_free (st=0x8241f90, func=0x4149c0b4 > <engine_cleanup_cb_free>) at stack.c:283
That is most peculiar. If an ENGINE isn't in use I wouldn't expect that to happen unless something somewhere is loading one. OK, next step is to see what ENGINE it is. Can you in the debugger print out the engine structure for example in frame #5? Steve. -- 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 [email protected] Automated List Manager [email protected]
