John Foley <fol...@cisco.com> writes: > If you add the --show-reachable option to valgrind, you can see where > the leaks originate. They appear to be in the ex_data code (see > below). As a side note, I see 416 bytes lost when using OpenSSL 1.0.1f > as well as 1.0.2a.
Ah, I forgot to mention. I'm not concerned about the leak, but the invalid read that's in 1.0.2 only. This one: >> ==14854== Invalid read of size 2 >> ==14854== at 0x4F09198: bn_get_bits5 (in >> /home/henribak/src/thirdparty/openssl/libcrypto.so.1.0.0) >> ==14854== by 0x4F32B47: generate_key (in >> /home/henribak/src/thirdparty/openssl/libcrypto.so.1.0.0) >> ==14854== by 0x400A30: main (in /home/henribak/tmp/dh-1.0.2) -- Henrik Grindal Bakken <h...@ifi.uio.no> PGP ID: 8D436E52 Fingerprint: 131D 9590 F0CF 47EF 7963 02AF 9236 D25A 8D43 6E52 _______________________________________________ openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev