The branch OpenSSL_1_1_0-stable has been updated
via 0d325d9cb9ecb10cb1d41f64751ca8d8f2df472b (commit)
from 2cf10e88b7221e1edbbdc8ecc89abe2953a668b1 (commit)
- Log -----------------------------------------------------------------
commit 0d325d9cb9ecb10cb1d41f64751ca8d8f2df472b
Author: Rich Salz <rs...@openssl.org>
Date: Thu Nov 3 13:16:26 2016 -0400
Update CRYPTO_set_mem_debug() doc
Reviewed-by: Richard Levitte <levi...@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/1842)
(cherry picked from commit 00bb5504cc62693e05ff4e699f379011c55ecc84)
-----------------------------------------------------------------------
Summary of changes:
doc/crypto/OPENSSL_malloc.pod | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/doc/crypto/OPENSSL_malloc.pod b/doc/crypto/OPENSSL_malloc.pod
index 50f0975..2104f43 100644
--- a/doc/crypto/OPENSSL_malloc.pod
+++ b/doc/crypto/OPENSSL_malloc.pod
@@ -135,8 +135,10 @@ at build-time).
This adds some overhead by keeping a list of all memory allocations, and
removes items from the list when they are free'd.
This is most useful for identifying memory leaks.
-CRYPTO_set_mem_debug() turns this tracking on and off. It is normally
-called at startup, but can be called at any time.
+CRYPTO_set_mem_debug() turns this tracking on and off. In order to have
+any effect, is must be called before any of the allocation functions
+(e.g., CRYPTO_malloc()) are called, and is therefore normally one of the
+first lines of main() in an application.
CRYPTO_mem_ctrl() provides fine-grained control of memory leak tracking.
To enable tracking call CRYPTO_mem_ctrl() with a B<mode> argument of
_____
openssl-commits mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-commits
