Rich Salz f7edeced4d Add "random malloc failure" tooling ... Still needs to be documented, somehow/somewhere. The env var OPENSSL_MALLOC_FAILURES controls how often malloc/realloc should fail. It's a set of fields separated by semicolons. Each field is a count and optional percentage (separated by @) which defaults to 100. If count is zero then it lasts "forever." For example: 100;@25 means the first 100 allocations pass, then the rest have a 25% chance of failing until the program exits or crashes. If env var OPENSSL_MALLOC_FD parses as a positive integer, a record of all malloc "shouldfail" tests is written to that file descriptor. If a malloc will fail, and OPENSSL_NO_CRYPTO_MDEBUG_BACKTRACE is not set (platform specific), then a backtrace will be written to the descriptor when a malloc fails. This can be useful because a malloc may fail but not be checked, and problems will only occur later. Reviewed-by: Richard Levitte <levitte@openssl.org> (Merged from https://github.com/openssl/openssl/pull/1252)		2017-01-12 11:27:27 -05:00
..
asn1_int.h	PSS ASN.1 method	2017-01-08 01:42:46 +00:00
async.h
bn_conf.h.in
bn_dh.h
bn_int.h
bn_srp.h
chacha.h
cryptlib_int.h	Add "random malloc failure" tooling	2017-01-12 11:27:27 -05:00
cryptlib.h
dso_conf.h.in
engine.h
err_int.h
evp_int.h	PSS EVP_PKEY method	2017-01-08 01:42:47 +00:00
md32_common.h
objects.h
poly1305.h
rand.h
x509_int.h	Add support for reference counting using C11 atomics	2016-11-17 22:02:25 +01:00