As response to a user request to be able to use external memory

handling routines that need file name and line number information,
I've added a call level to our memory handling routines to allow that
kind of hooking.

1 files changed, 25 insertions, 0 deletions

diff --git a/CHANGES b/CHANGES
index e5371b98dc..77ad4d16f7 100644
--- a/CHANGES
+++ b/CHANGES
@@ -3,6 +3,31 @@
 
  Changes between 0.9.6 and 0.9.7  [xx XXX 2000]
 
+  *) Add another call level for memory allocation routines, thereby
+     allowing memory allocation callbacks that can be given file
+     name and line number information.  The basic functionality
+     remains, as well as the original possibility to just replace
+     malloc(), realloc() and free().  The new functions that can be
+     registered help users provide variants of malloc(), realloc()
+     and free() that take two extra arguments, a const char* and an
+     int.  To register and find out the current settings for those
+     hooks, the following functions are provided:
+
+	CRYPTO_set_mem_ex_functions
+	CRYPTO_set_locked_mem_ex_functions
+	CRYPTO_get_mem_ex_functions
+	CRYPTO_get_locked_mem_ex_functions
+
+     They work the same way as the corresponding CRYPTO_set_mem_functions
+     and friends with one exception: giving NULL as arguments will restore
+     the internal hooks to internal routines and will still make the above
+     functions return 1 and not 0.
+
+     This functionality was created as a direct request to add the
+     possibility to interface with the Windows debugging routines
+     _malloc_dbg, _realloc_dbg and _free_dbg.
+     [Richard Levitte]
+
   *) Fix to uni2asc() to cope with zero length Unicode strings.
      These are present in some PKCS#12 files.
      [Steve Henson]