moin, when running my application under valgrind, i get a bazillion of different reports of this type:
==9223== Conditional jump or move depends on uninitialised value(s) ==9223== at 0x4C2AFC1: bcmp (mc_replace_strmem.c:891) ==9223== by 0x55170B4: aesni_cbc_hmac_sha1_cipher (e_aes_cbc_hmac_sha1.c:269) ==9223== by 0x51DDB8E: tls1_enc (t1_enc.c:828) ==9223== by 0x51D572F: ssl3_read_bytes (s3_pkt.c:405) ==9223== by 0x51D2CFF: ssl3_read_internal (s3_lib.c:4207) ... ==9583== Uninitialised value was created by a stack allocation ==9583== at 0x54AD3F7: aesni_cbc_encrypt (aesni-x86_64.s:2081) reading the code reveals that this is right after a return from a function. preliminary discussion with the valgrind folks suggests that this code may be violating the ABI by storing data below the reserved stack frame. apart from making valgrind mostly useless, this is very bad idea, as asynchronously delivered signals may mess up the stack. is it possible to suppress the use of this (over-)optimized cipher routine via the environment/configuration? regards ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [email protected] Automated List Manager [email protected]
