Skip to content
  1. Jan 21, 2000
  2. Jan 20, 2000
  3. Jan 19, 2000
  4. Jan 16, 2000
  5. Jan 13, 2000
  6. Jan 12, 2000
  7. Jan 11, 2000
  8. Jan 09, 2000
  9. Jan 08, 2000
  10. Jan 07, 2000
  11. Jan 06, 2000
  12. Jan 02, 2000
  13. Jan 01, 2000
  14. Dec 29, 1999
  15. Dec 26, 1999
  16. Dec 24, 1999
  17. Dec 23, 1999
  18. Dec 22, 1999
  19. Dec 19, 1999
  20. Dec 18, 1999
    • Richard Levitte's avatar
      - Added more documentation in CHANGES. · f3a2a044
      Richard Levitte authored
       - Made CRYPTO_MDEBUG even less used in crypto.h, giving
         MemCheck_start() and MemCheck_stop() only one possible definition.
       - Made the values of the debug function pointers in mem.c dependent
         on the existence of the CRYPTO_MDEBUG macro, and made the rest of
         the code understand the NULL case.
      
      That's it.  With this code, the old behvior of the debug functionality
      is restored, but you can still opt to have it on, even when the
      library wasn't compiled with a defined CRYPTO_MDEBUG.
      f3a2a044
    • Richard Levitte's avatar
      - Made sure some changed behavior is documented in CHANGES. · d8df48a9
      Richard Levitte authored
       - Moved the handling of compile-time defaults from crypto.h to
         mem_dbg.c, since it doesn't make sense for the library users to try
         to affect this without recompiling libcrypto.
       - Made sure V_CRYPTO_MDEBUG_TIME and V_CRYPTO_MDEBUG_THREAD had clear
         and constant definitions.
       - Aesthetic correction.
      d8df48a9
  21. Dec 17, 1999
    • Richard Levitte's avatar
      Rebuild of the OpenSSL memory allocation and deallocation routines. · 9ac42ed8
      Richard Levitte authored
      With this change, the following is provided and present at all times
      (meaning CRYPTO_MDEBUG is no longer required to get this functionality):
      
        - hooks to provide your own allocation and deallocation routines.
          They have to have the same interface as malloc(), realloc() and
          free().  They are registered by calling CRYPTO_set_mem_functions()
          with the function pointers.
      
        - hooks to provide your own memory debugging routines.  The have to
          have the same interface as as the CRYPTO_dbg_*() routines.  They
          are registered by calling CRYPTO_set_mem_debug_functions() with
          the function pointers.
      
      I moved everything that was already built into OpenSSL and did memory
      debugging to a separate file (mem_dbg.c), to make it clear what is
      what.
      
      With this, the relevance of the CRYPTO_MDEBUG has changed.  The only
      thing in crypto/crypto.h that it affects is the definition of the
      MemCheck_start and MemCheck_stop macros.
      9ac42ed8
  22. Dec 11, 1999
  23. Dec 10, 1999
  24. Dec 05, 1999