diff options
author | Richard Levitte <levitte@openssl.org> | 2005-03-23 21:14:59 +0000 |
---|---|---|
committer | Richard Levitte <levitte@openssl.org> | 2005-03-23 21:14:59 +0000 |
commit | 6141b86a49e5470556a912ca984b86ecd70d44f1 (patch) | |
tree | 2d2ed734e55e9134b2fe17aecd42556ae3e9bbd2 /FAQ | |
parent | 23fadaa0845ff706e2ff7e1b3d5fe351dfbbedc1 (diff) | |
download | openssl-6141b86a49e5470556a912ca984b86ecd70d44f1.tar.gz |
Change the memory leak FAQ entry to describe the levels of thread safety in each function
Diffstat (limited to 'FAQ')
-rw-r--r-- | FAQ | 17 |
1 files changed, 14 insertions, 3 deletions
@@ -793,9 +793,20 @@ that is allocated when an application starts up. Since such tables do not grow in size over time they are harmless. These internal tables can be freed up when an application closes using various -functions. Currently these include: EVP_cleanup(), ERR_remove_state(), -ERR_free_strings(), ENGINE_cleanup(), CONF_modules_unload() and -CRYPTO_cleanup_all_ex_data(). +functions. Currently these include following: + +Thread-local cleanup functions: + + ERR_remove_state() + +Application-global cleanup functions that are aware of usage (and therefore +thread-safe): + + ENGINE_cleanup() and CONF_modules_unload() + +"Brutal" (thread-unsafe) Application-global cleanup functions: + + ERR_free_strings(), EVP_cleanup() and CRYPTO_cleanup_all_ex_data(). =============================================================================== |