From 460185d754fc7e31924f6209155ed38beb3a84de Mon Sep 17 00:00:00 2001 From: Miod Vallat Date: Tue, 8 Jul 2014 20:26:06 +0000 Subject: Do not suggest using BUF_strdup() preferably to strdup() for fallacious reasons. --- lib/libssl/src/doc/crypto/BUF_MEM_new.pod | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/lib/libssl/src/doc/crypto/BUF_MEM_new.pod b/lib/libssl/src/doc/crypto/BUF_MEM_new.pod index b761859086d..a83f46f8968 100644 --- a/lib/libssl/src/doc/crypto/BUF_MEM_new.pod +++ b/lib/libssl/src/doc/crypto/BUF_MEM_new.pod @@ -45,10 +45,7 @@ B. Any data already in the buffer is preserved if it increases in size. BUF_strdup() copies a null terminated string into a block of allocated memory -and returns a pointer to the allocated block. Unlike the standard C library -strdup() this function uses OPENSSL_malloc() and so should be used in -preference to the standard library strdup() because it can be used for memory -leak checking or replacing the malloc() function. +and returns a pointer to the allocated block. The memory allocated from BUF_strdup() should be freed up using the OPENSSL_free() function. -- cgit v1.2.3