From: Randy Wright <[EMAIL PROTECTED]>
rw26> I know that malloc is not reentrant. However, if somewhere in the openssl
rw26> libraries malloc is also called, perhaps that is when I get this crash.
Yes, OpenSSL uses malloc by default. I think it is generally assumed
that any OS that supports threads also has to support malloc() for
threads, since that would be a quite common operation. That mean that
if the OS implementors have done their job, their malloc()
implementation will use a mutex (I really don't see any other way to
implement it).
However, should you dislike that, it's perfectly possible for you to
implement your own malloc(), free() and realloc() and "register" them
with CRYPTO_set_mem_functions() (declared in crypto.h), generally
available since a month or so in 0.9.5-dev.
--
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
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
Re: alignment and thread problem - solaris
Richard Levitte - VMS Whacker Fri, 21 Jan 2000 17:07:56 -0800
- alignment and thread problem - solaris Randy Wright
- Re: alignment and thread problem - sola... Goetz Babin-Ebell
- Re: alignment and thread problem - sola... Richard Levitte - VMS Whacker
- Re: alignment and thread problem - ... Randy Wright
- Re: alignment and thread proble... Richard Levitte - VMS Whacker
- Re: alignment and thread problem - sola... Goetz Babin-Ebell
