> [[email protected] - Thu Jul 15 16:32:31 2010]: > > He are the debugging symbols. >
OK, the interesting bit is here: #0 0x00007ffff215ec60 in sha1_md () from /lib/libcrypto.so.0.9.8 #1 0x00007ffff1eac309 in engine_unlocked_init (e=0x7ffff863f550) at eng_init.c:67 Can you print out the value of 'e' from frame #1? I'm not sure why frame #0 isn't showing any more info, there's something odd going on there if that trace isn't totally corrupted it shouldn't be calling sha1_md() at all AFAICS. 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]
