>> Hi. I use OpenSSL in some of my applications and I noticed that sometimes >> (I could say less then 2% times I run it) it crashed without apparent >> reason, but lately it happened ALWAYS, without any changes on the > program, >> what's very strange. So I decided to track this bug, and I "almost" found >> it... My program crashes when it called SSL_connect(), I tought it > were my >> code but tried hard to fix it and was completely unsuccessful. So I > decided >> to start debuging the OpenSSL internals and started placing some hooks... >> I discovered where exactly the crash ocurred: >> >> <snip>.... > > I believe I am experiencing a similar crash as reported by a post > using this same subject (I had initially ignored the e-mail). > <snip>
Actually, this looks like its my fault, not creating the locks for OpenSSL threading. Just odd this behavior wasn't exhibited on any other machines. The Windows machine was a quad core box, and the only multi-core box we've tested on Windows (though other platforms have had tests with multi-core/cpu boxes). I did have a question though. Is there any reason to define the dynamic thread locking functions? There is a note stating: "Also, dynamic locks are currently not used internally by OpenSSL, but may do so in the future." Is this still accurate? If OpenSSL does start to use them internally, will the 'old-style' still be sufficient (but maybe just not optimal), or will there be undefined behavior? Thanks. -Brad ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [email protected] Automated List Manager [EMAIL PROTECTED]
