From 471cb1a71c9be6c2aa1b1c74bdd8965585a868ff Mon Sep 17 00:00:00 2001 From: miod <> Date: Tue, 8 Jul 2014 20:26:05 +0000 Subject: Do not suggest using BUF_strdup() preferably to strdup() for fallacious reasons. --- src/lib/libssl/src/doc/crypto/BUF_MEM_new.pod | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) (limited to 'src/lib') diff --git a/src/lib/libssl/src/doc/crypto/BUF_MEM_new.pod b/src/lib/libssl/src/doc/crypto/BUF_MEM_new.pod index b761859086..a83f46f896 100644 --- a/src/lib/libssl/src/doc/crypto/BUF_MEM_new.pod +++ b/src/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-55-g6feb