I'm not sure I understand the use or purpose of CRYPTO_malloc_locked()
and friends.  Is it meant to be used for some kind of special locking,
other than the locking that correctly implemented OS's have in their
allocation routines?

As far as I can see, CRYPTO_malloc_locked and friends are only used in
crypto/rsa/rsa_lib.c (masqueraded as Malloc_locked() and Free_locked()).

If it's supposed to be used for extra locking, wouldn't reimplementing
them to use the OpenSSL locking routines be a good thing?

The reason I'm asking is that I want to put some debugging code around
the actual call to malloc_locked_func(), and it feels that code should
be inside the lock as well...

-- 
Richard Levitte   \ Spannv�gen 38, II \ [EMAIL PROTECTED]
Redakteur@Stacken  \ S-161 43  BROMMA  \ T: +46-8-26 52 47
                    \      SWEDEN       \ or +46-708-26 53 44
Procurator Odiosus Ex Infernis             -- [EMAIL PROTECTED]

Unsolicited commercial email is subject to an archival fee of $400.
See <http://www.stacken.kth.se/~levitte/mail/> for more info.
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Development Mailing List                       [EMAIL PROTECTED]
Automated List Manager                           [EMAIL PROTECTED]

Reply via email to