On Tue, May 02, 2006 at 08:08:10AM +0200, Marco Roeland wrote: > On Tuesday May 2nd 2006 at 00:34 Ulf Möller wrote: > > > Not much. If it helps with debugging, I'm in favor of removing them. > > (However the last time I checked, valgrind reported thousands of bogus > > error messages. Has that situation gotten better?) > > I recently compiled vanilla OpenSSL 0.9.8a with -DPURIFY=1 and on Debian > GNU/Linux 'sid' with valgrind version 3.1.1 was able to debug some > application using both TLS/SSL as S/MIME without any warning or error > about the OpenSSL code. Without -DPURIFY you're indeed flooded with > warnings. > > So yes I think not using the uninitialized memory (it's only a single > line, the other occurrence is already commented out) helps valgrind.
Afaik, both are actually being used, the one without the #ifndef PURIFY just doesn't seem to be used that much. Kurt ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager [EMAIL PROTECTED]
