Richard Levitte e077455e9e Stop raising ERR_R_MALLOC_FAILURE in most places ... Since OPENSSL_malloc() and friends report ERR_R_MALLOC_FAILURE, and at least handle the file name and line number they are called from, there's no need to report ERR_R_MALLOC_FAILURE where they are called directly, or when SSLfatal() and RLAYERfatal() is used, the reason `ERR_R_MALLOC_FAILURE` is changed to `ERR_R_CRYPTO_LIB`. There were a number of places where `ERR_R_MALLOC_FAILURE` was reported even though it was a function from a different sub-system that was called. Those places are changed to report ERR_R_{lib}_LIB, where {lib} is the name of that sub-system. Some of them are tricky to get right, as we have a lot of functions that belong in the ASN1 sub-system, and all the `sk_` calls or from the CRYPTO sub-system. Some extra adaptation was necessary where there were custom OPENSSL_malloc() wrappers, and some bugs are fixed alongside these changes. Reviewed-by: Tomas Mraz <tomas@openssl.org> Reviewed-by: Hugo Landau <hlandau@openssl.org> (Merged from https://github.com/openssl/openssl/pull/19301)		2022-10-05 14:02:03 +02:00
..
build.info
ct_b64.c	Stop raising ERR_R_MALLOC_FAILURE in most places	2022-10-05 14:02:03 +02:00
ct_err.c
ct_local.h
ct_log.c	Stop raising ERR_R_MALLOC_FAILURE in most places	2022-10-05 14:02:03 +02:00
ct_oct.c	Stop raising ERR_R_MALLOC_FAILURE in most places	2022-10-05 14:02:03 +02:00
ct_policy.c	Stop raising ERR_R_MALLOC_FAILURE in most places	2022-10-05 14:02:03 +02:00
ct_prn.c
ct_sct_ctx.c	Stop raising ERR_R_MALLOC_FAILURE in most places	2022-10-05 14:02:03 +02:00
ct_sct.c	Stop raising ERR_R_MALLOC_FAILURE in most places	2022-10-05 14:02:03 +02:00
ct_vfy.c
ct_x509v3.c