> Dismissing leaks as one-off's is a pet peeve of mine. The notion
> of one-off
> leaks in an executable is arguably passable, but becomes a plain
> old memory
> leak just like any other when packaged as a library.
Not if the memory is reused if the library is unloaded and reloaded.
How would you handle TSD, for example? There is no *portable* way to
hook
the destruction of a thread.
DS
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager [EMAIL PROTECTED]
