Deprecate most of debug-memory
Fixes #8322 The leak-checking (and backtrace option, on some platforms) provided by crypto-mdebug and crypto-mdebug-backtrace have been mostly neutered; only the "make malloc fail" capability remains. OpenSSL recommends using the compiler's leak-detection instead. The OPENSSL_DEBUG_MEMORY environment variable is no longer used. CRYPTO_mem_ctrl(), CRYPTO_set_mem_debug(), CRYPTO_mem_leaks(), CRYPTO_mem_leaks_fp() and CRYPTO_mem_leaks_cb() return a failure code. CRYPTO_mem_debug_{malloc,realloc,free}() have been removed. All of the above are now deprecated. Merge (now really small) mem_dbg.c into mem.c Reviewed-by: Paul Dale <paul.dale@oracle.com> Reviewed-by: Richard Levitte <levitte@openssl.org> (Merged from https://github.com/openssl/openssl/pull/10572)
This commit is contained in:
parent
4e3ee452d0
commit
742ccab318
28 changed files with 113 additions and 774 deletions
4
CHANGES
4
CHANGES
|
@ -41,6 +41,10 @@
|
|||
(CVE-2019-1551)
|
||||
[Andy Polyakov]
|
||||
|
||||
*) Most memory-debug features have been deprecated, and the functionality
|
||||
replaced with no-ops.
|
||||
[Rich Salz]
|
||||
|
||||
*) Introduced a new method type and API, OSSL_SERIALIZER, to
|
||||
represent generic serializers. An implementation is expected to
|
||||
be able to serialize an object associated with a given name (such
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue